fix(angular): router compatibility with Angular 12/13

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Some docs updates need to be made in the ionic-docs repo, in a separate PR. See the contributing guide for details.
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

In 6.1.9 we shipped a change to the router to support Angular 14. In routing scenarios where the component is injected into the root ion-router-outlet, the component factory resolver instance is null and causes the routing logic to fallback to the new Angular 14 behavior.

This results in routing throwing an exception and not routing the user/rendering the view.

Issue URL: #25448

What is the new behavior?

• Re-adds the fallback to the router outlet's component factory resolver when the supplied value is unset
• Angular 12/13 applications can route to root routes in an ion-router-outlet.

Does this introduce a breaking change?

• Yes
• No

Other information

Dev-build: 6.1.10-dev.11654882801.1eb62ed9 ✅