fix(compiler-cli): use inline type-check blocks for components outside rootDir

[JoostK]

An inline type-check block is required when a reference to a component class
cannot be emitted from an ngtypecheck shim file, but the logic to detect this
situation did not consider the configured rootDir. When a rootDir is
configured the reference emitter does not allow generating an import outside
this directory, which meant that a shim file wouldn't be able to reference
the component class. Consequently, type-check block generation would fail
with a fatal error that is unaccounted for, as gathering diagnostics should
be non-fallible.

This commit fixes the problem by leveraging the existing canReferenceType
logic of the type-checking Environment, instead of the rudimentary check
whether the class is exported as top-level symbol (checkIfClassIsExported).
Instead, canReferenceType pre-flights the generation of an import using the
ReferenceEmitter to tell exactly whether it will succeed or not; thus taking
into account the rootDirs constraint as well.

Fixes #44999

[jessicajaniuk]

This PR was merged into the repository by commit f35f475.

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