fix(compiler-cli): clear un-fingerprinted preprocessor cache and lazy parser closures - #71930

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.dev application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Follows up on #71904:

1. In HybridCompiler.invalidateStaleFileAnalysis, moving existing.boundFingerprint = nextFingerprint outside the clearing if block while keeping existing.boundFingerprint !== undefined && existing.boundFingerprint !== nextFingerprint allows an un-fingerprinted fileCache entry (boundFingerprint === undefined, such as one populated by a direct processFileSync call) to be stamped with a valid boundFingerprint without clearing stale parsedTemplates, preparedTcbData, or tcb when a dependency's <ng-content> selectors change. Similarly, populateBoundData did not reset fileAnalysis.tcb, leaving stale TCB text for getTcbForFile when re-binding an un-fingerprinted entry.
2. In parseComponentTemplate, the lazy diagNodes getter shared parseComponentTemplate's closure context, keeping the containing .ts file content, ComponentMetadata, and parse options alive on cached ParsedComponentTemplate entries even for external templates and even after diagNodes had already been evaluated.

Issue Number: N/A

What is the new behavior?

1. HybridCompiler.invalidateStaleFileAnalysis compares existing.boundFingerprint !== nextFingerprint directly so transitioning from undefined to a computed fingerprint clears stale cached state before stamping nextFingerprint (while keeping (undefined, undefined) intact), and populateBoundData clears fileAnalysis.tcb = undefined whenever preparedTcbData is recomputed.
2. parseComponentTemplate isolates the lazy diagNodes parser closures into createInlineDiagParser and createExternalDiagParser (avoiding capturing ComponentMetadata, and avoiding capturing .ts content for external/indirect templates) and defineLazyDiagNodes clears the parser closure reference once diagNodes is evaluated.

Does this PR introduce a breaking change?

• Yes
• No

Other information