This is needed by rules_angular as otherwise these two packages are not present in the `npm_package_store_infos` using in the symlink package.

- Update `rules_angular` to `46fdabe25ad865093d1be752c778ca4d81f222f5`
- Update `devinfra` to `583cd52fbbadae28ca7a4dd55d63978a984c371a`
- Update `rules_browsers` to `dc3e432662fe9f99eb7f030a35a22d4ff77d54c7`
- Remove unused `rules_sass` dependency

This avoids the following error for projects using Vitest and Browser mode:

```
 Unhandled Error:
  Error: [(chrome)] Browser "chrome" is not supported by the browser provider "playwright". Supported
  browsers: firefox, webkit, chromium.
```

(cherry picked from commit 0d984cf)

See associated pull request for more information.

This change introduces a validation check in the Vitest runner to ensure that code coverage is only enabled when using supported Chromium-based browsers. Since the Angular CLI integration currently relies exclusively on the V8 coverage provider, running tests in non-Chromium browsers like Firefox or Safari with coverage enabled would result in incomplete data or missing reports. By adding this check, developers will receive a clear, actionable error message early in the process, preventing confusion and ensuring reliable coverage reports.

(cherry picked from commit 74e7dbe)

… scan

File crawling concurrency occasionally surfaces temporary EBADF descriptors on specialized filesystems. This catches and ignores them, guaranteeing completion of background discovery loops.

(cherry picked from commit ead60d3)

… inside MCP tools

The MCP server host runtime now dynamically resolves the precise Angular CLI binary from the workspace's node_modules rather than relying on global system path invocations. This guarantees full compatibility between a project's specific configuration constraints and the active framework version, preventing mismatches across monorepos or containerized setups.

(cherry picked from commit cc30034)

See associated pull request for more information.

See associated pull request for more information.

… prerender builder

Ensures that the route always starts with a leading slash when calling the render function, preventing potential issues with relative paths or incorrect URL resolution during prerendering.

(cherry picked from commit 30d8332)

See associated pull request for more information.

This was commited by mistake.

(cherry picked from commit 9d0e656)

improve package resolution

- In the `app-shell` builder, ensure the route URL has a leading slash.
- In webpack helpers, use `createRequire` in `isPackageInstalled` to improve package resolution robustness.

(cherry picked from commit cf5b49e)

…ution

Use `compilerOptions.rootDir` when calculating the relative path for HMR component updates, falling back to the current directory if not set. This ensures correct path resolution when `rootDir` is configured in `tsconfig`.

Closes #33005 and closes #32998

(cherry picked from commit 59803b1)

See associated pull request for more information.

…e#buildUndefinedNode`

Babel 8 is _likely_ going to remove the variant on `Scope#`, since this method has not needed scope-specific information in ages.

(cherry picked from commit 8b62c18)

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.