(cherry picked from commit f8576e3)

See associated pull request for more information.

See associated pull request for more information.

The scorecard workflow has been replaced at the org level so these changes remove it from our workflows.

(cherry picked from commit a9e507a)

…er bundles

Back in-memory server bundles with SharedArrayBuffer to eliminate V8 structuredClone
memory duplication across worker threads and loader hooks.

Batch routes dynamically during prerendering to amortize IPC messaging and event
loop scheduling overhead.

(cherry picked from commit 62999ca)

See associated pull request for more information.

In libraries built with ng-packagr, `package.json` typically specifies
`"sideEffects": false` so consumer applications can tree-shake unused code.
However, when executing unit tests through `@angular/build:unit-test`, the
test builder bundles workspace library source directly (via tsconfig paths).

Because esbuild tree-shaking respects `"sideEffects": false` annotations in the
enclosing `package.json`, bundling multiple spec entry points without splitting
can cause esbuild to prune module bodies (such as component definitions) from
multi-level `export *` barrel graphs while retaining namespace re-export
accessors. At runtime, accessing the exported symbols evaluates to `undefined`,
causing failures such as `TypeError: Cannot read properties of undefined (reading 'ɵcmp')`.

Test bundles are executed locally in memory and never distributed over the wire,
so side-effect annotations and pure call pruning are not required. Setting
`ignoreAnnotations: true` when `disableCodeSplitting` is enabled ensures that
statically reachable barrel exports in workspace code are retained without
affecting production application or package builds.

Closes #33910

(cherry picked from commit 4d0be68)

See associated pull request for more information.