See associated pull request for more information.

… in dev mode

This commit introduces the `keepNames` option in esbuild configurations for both application code bundling and Vite utility functions.

By setting `keepNames` to `true` (or conditionally based on optimization settings), function and variable names are preserved during the build process. This significantly improves the debugging experience in **development mode** by ensuring that original names are retained in compiled output, leading to more readable stack traces and easier identification of code sections during development.

(cherry picked from commit 58da860)

See associated pull request for more information.

See associated pull request for more information.

…le checks

This commit refactors the package manager lockfile detection logic to:
- Introduce a `LOCKFILE_NAMES` constant for better maintainability and clarity.
- Enhance Bun lockfile detection by checking for both `bun.lockb` and `bun.lock`.
- Optimize lockfile checks by reading the root directory files once and passing them to the `hasLockfile` method, reducing redundant file system operations.

This addresses issues where Bun lockfiles might not have been correctly identified.

closes #31128

(cherry picked from commit 2037b91)

The `LOCKFILE_NAMES` constant in `packages/angular/cli/src/utilities/package-manager.ts` is updated to explicitly exclude `PackageManager.Cnpm` from its type definition. This refactors the type to accurately reflect the package managers supported by the lockfile detection logic.

See associated pull request for more information.

This commit updates the `runs-on` configuration in the CI workflows (`ci.yml`, `pr.yml`) from specific `ubuntu-latest-Xcore` labels to the more general `ubuntu-latest`. This change reduces resource consumption. This change should not be needed for RBE and remote cache.

(cherry picked from commit 1578402)

In SSR applications, an unnecessary event loop tick during server startup could lead to an incorrect platform being initialized.

This change introduces an `ngJitMode` define, which is set to `false` during AOT builds. This allows for the JIT-specific code paths to not be followed, preventing the async operations that caused the extra tick. This ensures that the server platform is correctly and synchronously initialized.

(cherry picked from commit 9749ec6)

The labels in the `ai-config` schematic were not aligned, this commit fixes the alignment.

(cherry picked from commit ddebe3d)

…de rendering

This commit introduces a number of changes to the server bootstrapping process to make it more robust and less error-prone, especially for concurrent requests.

Previously, the server rendering process relied on a module-level global platform injector. This could lead to issues in server-side rendering environments where multiple requests are processed concurrently, as they could inadvertently share or overwrite the global injector state.

The new approach introduces a `BootstrapContext` that is passed to the `bootstrapApplication` function. This context provides a platform reference that is scoped to the individual request, ensuring that each server-side render has an isolated platform injector. This prevents state leakage between concurrent requests and makes the overall process more reliable.

BREAKING CHANGE:
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.

Before:
```ts
const bootstrap = () => bootstrapApplication(AppComponent, config);
```

After:
```ts
const bootstrap = (context: BootstrapContext) =>
  bootstrapApplication(AppComponent, config, context);
```

Update FW packages to latest minor.