Resolves a test failure internally where we weren't matching how ngtsc emits `ctorParameters` for primitive types. It appears that in ngtsc we have some logic where `string` gets emitted as the `String` object, `number` as the `Number` object etc.

Interpolation renders null and undefined as an empty string instead of
converting them with toString. Attribute bindings remove the attribute for
undefined as well as null. The [class] binding does not drop strings that
are not valid CSS class names, so describe the string form instead.

Updated Angular adev cross repo docs files.

…onfigPath

`HybridCompiler` wrote `<tsconfig>.ngdiag.json` itself from `prepareChunk` and `prepareChunkSync`,
which tied it to a `tsconfigPath` and to the Node filesystem, or to a `virtualFiles` overlay
standing in for it. Now that the analyzer no longer requires a tsconfig, hosts that embed the
compiler without one have nowhere to write such a file, and whether and where diagnostics are
persisted is a decision for the build driver rather than for the compiler.

`tsconfigPath` and `virtualFiles` are therefore removed from `HybridCompilerOptions`, together
with `writeDiagnosticsFile` and `writeDiagnosticsFileSync`, and `hybrid_compiler.ts` no longer
imports `node:fs`. In their place, `HybridCompiler.getDiagnostics()` returns the collected
per-file diagnostics in the deterministic order the `.ngdiag.json` already used and leaves out
diagnostics anchored on `.d.ts` files unless `includeDeclarationFiles` is set, making it the
single place that filters and orders them; `serializeDiagnostics` now only formats that output.
The `.ngdiag.json` write moves into `run` in `ngp.ts`, gated on a new optional
`RunOptions.tsconfigPath`. The write that preceded the processing of each chunk is dropped as
redundant, while `run` still writes after every chunk and once more at the end so that option
diagnostics reach the file even when the analyzer produces no chunks.

Without a tsconfig there is also nothing to resolve relative paths against, so `rootDir` and
`rootDirs` on `HybridCompilerOptions` must now be absolute; relative `rootDirs` used to be
resolved against `rootDir` or `dirname(tsconfigPath)`. This matters because
`getProjectRelativePath`, which produces the `ɵsetClassDebugInfo` paths and HMR IDs, uses
`path.posix.relative` and would silently resolve a relative root against the process cwd. Both
options are normalized to forward slashes; `rootDir` previously was not, which would have broken
that computation for backslash paths on Windows. `main.ts` resolves relative `rootDirs` against
the tsconfig directory, matching TypeScript and the analyzer, and the test helpers do the same.

…orted constructor tokens in ngp

Align ngp with ngtsc by unconditionally emitting imported constructor
DI tokens and class metadata through module namespace imports (e.g.
i1.Service) instead of only doing so for @angular/core or in
complianceMode.

This removes the divergence and eliminates the need to pass complianceMode
to buildDeps or useCoreNamespace/complianceMode to buildCtorParametersExpr.

This reverts commit 3d5bfdf.
Also reverts follow-up commit 4690b54 (#71651).

The Oxc 0.144 -> 0.155 update in `ng-analyze` (#71599) requires a separate
dependency update in google3. Reverting to unblock google3 sync.