This seems to be timing out occasionally in CI.

(cherry picked from commit d96a093)

The esbuild builder has some logic that re-map diagnostics coming from the compiler, depending on their `source` and `code`. Currently this is incorrect, because it assumed that a value of `ngtsc` for `source` always means that the error is from the Angular compiler, but what it actually means is that it comes from an Angular template diagnostics. Furthermore, we can't rely on a `source` always being defined.

These changes align the logic to a similar one we already have in the compiler where we assume the diagnostic comes from Angular if it starts with `-99`.

(cherry picked from commit 1cde40e)

Remove proxy to handle `/` to `/base/` instead update the `AngularAssetsMiddleware`

Closes #30639

(cherry picked from commit 1aeefa7)

Now that the style guide recommends to use `inject()`, having a constructor in a service is not really useful.

(cherry picked from commit cefea43)

`yarn` is no longer used.

(cherry picked from commit cad1594)

…undling

Bundling this module causes unit tests to fail with `@vitest/browser/context can be imported only inside the Browser Mode. Your test is running in browser pool. Make sure your regular tests are excluded from the "test.include" glob pattern.`, This is because `@vitest/browser/context` is a virtual mode in vite and the package on NPM is dummy that is used for static analysis.

Closes: #30677
(cherry picked from commit 9e292f1)