Angular integration for label providers

[msmithNI]

Pull Request

🤨 Rationale

Partially addresses #1090 (Blazor changes will be a subsequent PR)

👩‍💻 Implementation

See the HLD for the implementation plan for the label providers.

This PR adds in nimble-angular:

• NimbleLabelProviderCoreDirective and NimbleLabelProviderTableDirective (standard wrappers)
• NimbleLabelProviderCoreWithDefaultsDirective and NimbleLabelProviderCoreWithDefaultsDirective: Apps will use these directives to automatically initialize the label providers with the localized strings (which use $localize from @angular/localize, which is now an optional peer dependency for nimble-angular)
• 2 new secondary entry points, @ni/nimble-angular/label-provider/core and @ni/nimble-angular/label-provider/table
  • In my prototype, until I added separate entry points, as soon as an app pulled in new nimble-angular version, Nimble's localized strings would be pulled into their resource files (even without depending on the new modules). Whereas, with secondary entry points, the app needs to explicitly import NimbleLabelProviderCoreModule and/or NimbleLabelProviderTableModule to get the strings pulled in, which seemed like better behavior.

🧪 Testing

• Added autotests for new directives
• Update Angular example app to pull in the label providers the same way apps will, i.e. <nimble-label-provider-core withDefaults></nimble-label-provider-core>. Note that there's not additional translation logic in the example app though, so this just uses the English strings (so basically a no-op, just there as an example).

✅ Checklist

• I have updated the project documentation to reflect my changes or determined no changes are needed.
  • Updated Readme and contributing docs for nimble-angular with Localization info

[jattasNI]

Changes look good to me but my vote is to wait for the deps update to go in and then clean up the package changes in this PR. So I'll wait to approve until after taking another look at the package files when that's done.