fix(cdk/portal): remove ComponentFactoryResolver usages

[crisbeto]

We now have all the necessary APIs to allow to remove our usages of the deprecated ComponentFactoryResolver.

Fixes #24334.

[crisbeto]

This one is blocked, because it caused some subtle DI behavior differences in g3 which break some tests.

[JvanderHeide]

I'm currently using this in a module federation setup in combination with ngx-translate.
When I leave out the component factory resolver, the component is mounted in the parent project (where the portal outlet is) and as such is missing the translations from my module.

However, when i explicitly add the componentFactoryResolver, my translations are loaded from my child project as it should in this case. ie. the component is rendered as if it was fully in my child project.

From how i just read these changes, it would seem that viewContainerRef should be sufficient to achieve the same? Is that correct?

[damianbeles]

@crisbeto any updates on this one?

[yahya-uddin]

Any update on this?

[markusahrweileramcon]

Can you please share the current state?

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