perf(core): use ngDevMode to tree-shake warnings

[arturovt]

This commit adds ngDevMode guard to show sanitization warnings only
in dev mode (similar to how things work in other parts of Ivy runtime code).
The ngDevMode flag helps to tree-shake these warnings from production builds
(in dev mode everything will work as it works right now) to decrease production bundle size.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Refactoring (no functional changes, no api changes)

Does this PR introduce a breaking change?

• Yes
• No

[AndrewKushnir]

The change looks good overall, thanks @arturovt, I just left a couple suggestions to take into account the fact that ngDevMode may be undeclared, so we should handle that. Thank you.

[AndrewKushnir]

Presubmit.

[mhevery]

reviewed-for: global-approvers

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     status "ci/circleci: test_aio_tools" is failing
     status "ci/circleci: test" is pending
     status "ci/circleci: test_aio" is pending
     status "ci/circleci: test_aio_local" is pending
     status "ci/circleci: test_aio_local_viewengine" is pending
     status "ci/circleci: test_win" is pending
     status "google3" is pending
     missing required status "ci/circleci: publish_snapshot"

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[mhevery]

reviewed-for: global-approvers

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}