…ntent

Inline `[contenthash:<digest>]`/`[chunkhash:<digest>]` re-encoded the
already-truncated stored hash, and in the dynamic chunk-filename runtime
module the digest re-encode mangled the per-chunk map, dropping the hash
entirely so dynamically-loaded chunks 404'd.

Retain the full content digest per chunk (transient, recomputed each seal)
and re-encode from it in both the static asset path and the per-chunk
runtime map, so the value carries full entropy and the runtime URL matches
the emitted filename. `[fullhash:<digest>]`/`[hash:<digest>]` in a
dynamically-loaded chunk filename now throws a clear error, since it resolves
to a runtime getFullHash() expression that cannot be re-encoded.

The base-N encoder dropped leading 0x00 bytes (whole digest collapsed to one
BigInt), so two distinct digests could collide and a zero-heavy digest encoded
far shorter than requested, making [contenthash:baseN:N] slices too short. Re-
emit one leading alphabet[0] char per leading zero byte (and decode the inverse),
matching the function's own documented contract. Digests without a leading zero
byte are unchanged, so typical output hashes are unaffected.

…full content

Inline [contenthash:<digest>]/[modulehash:<digest>] in module/asset contexts
(asset-module filenames) re-encoded the already-truncated stored hash, so the
digest carried no extra entropy and an inline length couldn't exceed
output.hashDigestLength. Thread the full content digest through AssetGenerator
into PathData (contentHashFull) and pass the full module hash (getModuleHash,
not getRenderedModuleHash), so the static re-encode uses full entropy — matching
the chunk-context behaviour added earlier.

[fullhash:<digest>]/[hash:<digest>] in a dynamically-loaded chunk filename
previously threw, because the runtime builds it from getFullHash() — a runtime
expression that cannot be re-encoded. When such a template is used, flag the
GetChunkFilenameRuntimeModule as fullHash so it re-renders after hashing, and
inline the re-encoded full compilation hash directly instead of getFullHash().
The inlined value is byte-identical to the statically emitted filename, so the
chunk loads with full entropy (no 404). The length-only [fullhash:8] form is
unchanged and still uses the getFullHash() runtime expression.

lint:types-test (tsc -p tsconfig.types.test.json) type-checks the test files;
the new cases passed synthetic object literals that don't satisfy PathData /
AssetInfo. Cast them with EXPECTED_ANY, matching the existing idiom in this file.