feat(core): allow to throw on unknown properties in tests

[cexbrayat]

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

What kind of change does this PR introduce?

• Feature

What is the current behavior?

In a test, when using an unknown property in a template, we just get a console error.

This is similar to PR #45479 which introduced an errorOnUnknownElements option.

Issue Number: #36430

What is the new behavior?

Allows to provide a TestBed option to throw on unknown properties in templates:

getTestBed().initTestEnvironment(
  BrowserDynamicTestingModule,
  platformBrowserDynamicTesting(), {
    errorOnUnknownProperties: true
  }
);

Does this PR introduce a breaking change?

• Yes
• No

The default value of errorOnUnknownProperties is false, so this is not a breaking change.

Other information

[AndrewKushnir]

@cexbrayat thanks for the followup PR! I've added a couple minor comments, but overall the change looks good 👍

[AndrewKushnir]

Presubmit.

[atscott]

reviewed-for: public-api

[AndrewKushnir]

Reviewed-for: public-api

[dylhunn]

(sorry, was updating labels on the wrong PR!)

@cexbrayat @ me as soon as the comments are fixed, and we can sneak this one into 14! :)

[cexbrayat]

@dylhunn @AndrewKushnir Thanks for the review: PR updated with your feedback!

[AndrewKushnir]

Merge-assistance: the necessary approvals were received, but reset due to an extra commit that addressed the feedback after the review. I've re-checked the code after the final update and things are looking good. The presubmit is "green", so the PR is now ready for merge.

[dylhunn]

This PR was merged into the repository by commit a667592.

[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.}