fix(compiler-cli): do not persist component analysis if template/styles are missing

[devversion]

Consider the following scenario:

1. A TS file with a component and templateUrl exists
2. The template file does not exist.
3. First build: ngtsc will properly report the error, via a FatalDiagnosticError
4. The template file is now created
5. Second build: ngtsc still reports the same errror.

Ngtsc persists the analysis data of the component and never invalidates it when the template/style
file becomes available later.

This breaks incremental builds and potentially common workflows where resource files are added
later after the TS file is created. This did not surface as an issue in the Angular CLI yet because Webpack
requires users to re-start the process when a new file is added. With ESBuild this will change and this
also breaks incremental builds with Bazel/Blaze workers.

To fix this, we have a few options:

• Invalidate the analysis when e.g. the template file is missing. Never caching it means that it will be
  re-analyzed on every build iteration.
• Add the resource dependency to ngtsc's incremental file graph. ngtsc will then know via host.getModifiedResources when the file becomes available- and fresh analysis of component would occur.

The first approach is straightforward to implement and was chosen here. The second approach would
allow ngtsc to re-use more of the analysis when we know that e.g. the template file still not there, but it
ncreases complexity unnecessarily because there is no single obvious resource path for e.g. a templateUrl.
The URL is attempted to be resolved using multiple strategies, such as TS program root dirs, or there is support
for a custom resolution through host.resourceNameToFileName.

It would be possible to determine some candidate paths and add them to the dependency tracker, but it
seems incomplete given possible external resolvers like resourceNameToFileName and also would likely
not have a sufficient-enough impact given that a broken component decorator is not expected to remain
for too long between N incremental build iterations.

[AndrewKushnir]

@devversion it looks like presubmit info is missing, could you please update the status or leave a comment about the presubmit state, so that we can proceed with the merge?

[devversion]

@AndrewKushnir started presubmit now. The caretaker queue filter should only show it when all statuses are green, but feel free to remove the label if you prefer that.

[AndrewKushnir]

This PR was merged into the repository by commit b6c6dfd.

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