feat(compiler-cli): inline resources when generating class metadata calls

[devversion]

Previously with View Engine output, the enableResourceInlining option
could be set to inline external templates and styles (also for the
resulting .metadata.json files). We want to do the same for the Ivy
compilation pipeline (regardless of the compilation mode). The full
compilation definitions, and partial declarations currently already
inline resources in a way that no external requests need to be made.

Although there is one exception currently. These are the calls for
setting class metadata (for testbed overrides). This commit updates
the set class metadata calls (for both partial and full compilation)
to always inline resources. This means that libraries do not need
to start shipping external styles/templates just for the
setClassMetadata calls.

Note: Only doing this for partial compilation has been considered, but
it seems like it would be simpler implementation-wise to do this for
full compilation as well. Given the external resources are already
inlined (through their ecmp definitions), it seems acceptable (or
even more aligned) to do the same for the set class metadata calls.

Also, it's worth noting that source mappings will not exist for the
case where we inline external resources. It would be possible to
generate mappings in some cases; but not all because the @Component
metadata could be built up using a spread operator etc. I believe it's
not worth the effort doing this (this will require a lot of logic and break for
various edge-cases).

[petebacondarwin]

Looks good @devversion - a minor tweak should reduce the noise in the test diffs, and also produce more compact output.

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