Enable Angular strictTemplates across the four core-web apps

Task

Re-enable Angular's strictTemplates across the four apps in core-web. It is false in all of them behind a TODO that points at an already-closed issue.

// apps/dotcms-ui/tsconfig.app.json — and the same block in the other three
"angularCompilerOptions": {
    // TODO(#35930): re-enable strictTemplates once Angular 22 template errors are fixed per app
    "strictTemplates": false
}

#35930 (Angular 21 → 22 migration) is CLOSED, so the condition that gated this flag has been met and the flag stayed off. Affected apps:

• apps/dotcms-ui
• apps/dotcdn
• apps/dotcms-block-editor
• apps/dotcms-binary-field-builder

Why this is its own issue and not part of the strict-mode rollout

The strict-mode epic (#35932) is complete: all 44 projects it tracks carry the six flags, and dotcms-ui — the last one — landed in #36957. strictTemplates is a different gate and was deliberately left out of that scope.

Two facts make it a separate project:

1. strictTemplates: true is already set in 27 libraries and is inert in every one of them. A library with no build target never has its templates compiled, so the flag does nothing there. The only place it takes effect is an app — and in all four apps it is false. So the workspace currently looks like it has strict templates in 27 places and actually has them in zero.

2. Most of the work is not in the app. Measured on this branch by flipping the flag in apps/dotcms-ui/tsconfig.app.json and running nx run dotcms-ui:build:production:

By diagnostic code:

Turning the flag on in dotcms-ui is therefore mostly work in ~27 libraries whose templates have never been type-checked, which is why it needs its own bottom-up rollout rather than a line in the dotcms-ui PR.

Proposed approach

Same shape as #35932, and for the same reason — keep each PR reviewable:

1. Go bottom-up through the dependency graph. A library's template errors only surface when an app compiles them, so fix the leaves first.
2. Per library, verify with a consuming app's build, not tsc -p. tsc -p does not check templates at all — this is the trap that CLAUDE.md documents, and it is what let these 430 accumulate.
3. Flip the app flags last, one app per PR.
4. Remove the four stale TODO(#35930) comments as each app lands.

Acceptance Criteria

• strictTemplates: true in all four apps' tsconfig.app.json
• nx run-many -t build green, including :build:production for each app
• The four TODO(#35930) comments removed
• No new @ts-expect-error / $any() escapes introduced in templates without a linked issue
• nx run-many -t test lint no worse than the pre-change baseline

Notes

• Measurement was taken on branch 35932-enable-strict-mode at 72f10fe5ac and reverted; that branch does not contain the flag change.
• Related: #35932 (strict mode rollout, complete), #35930 (Angular 22 migration, closed), #36957 (the PR that finished #35932).

Start with the four apps/*/tsconfig.app.json files named in the issue and measure failures with an app production build, beginning with nx run dotcms-ui:build:production. Work bottom-up through the dependency graph, verifying library fixes through a consuming app rather than tsc -p. Done means all four flags are true, stale TODOs are removed, and the specified build, test, and lint commands meet the baseline.