Updates the linker integration test, which is an additional test we
run for the linker, besides running our tests with the linker.

The linker integration test ensures that the NPM package partial
compilation output can be processed properly, and ensures that there
are no unprocessable partial declarations.

(cherry picked from commit 18d549e)

(cherry picked from commit 7c1e975)

…3875)

This commit fixes that the Github actions currently may cache undesired
files. e.g. when Bazel runs the `dist/` folder is populated and
symlinked with the execroot, where another clone of the `node_modules`
would be cached accidentally then. We use an explicit path instead of a
pattern as it has been recommended by the Github action documentation.

Additionally, we fix that the dev-app building on RBE occurs with 2
concurrent jobs due to the host containers only having 2 cores. We can
run more jobs in the RBE containers.

(cherry picked from commit acd5ee1)

Updates framework packages to v13.0.0 and the CLI to v13.0.1. This
ensures our integration tests run with a stable version.

(cherry picked from commit 22d092e)

(cherry picked from commit df89f0d)

…ces (#23901)

Fixes that examples do not properly recognize webcontainer Stackblitz
instances. This causes some sidenav examples to not even work within
Stackblitz as a message `Please open on Stackblitz` is displayed.

Fixes #23895.

(cherry picked from commit e7a3f68)

* docs: add detailed breaking change note for Sass tilde change

Adds a detailed breaking change note for the Sass tilde change,
and cleans up some other auto-generated notes.

* fixup! docs: add detailed breaking change note for Sass tilde change

use permalink

(cherry picked from commit 3240a50)

…leftovers (#23899)

* build: remove unused code from legacy tooling and remove viewengine leftovers

Removes unused code from legacy tooling and View Engine compilation
within Bazel.

Also the clang-format file is removed given that we run prettier
in the whole repository now.

* fixup! build: remove unused code from legacy tooling and remove viewengine leftovers

ds

(cherry picked from commit be9abca)

In #23636 the test environment check was changed so that it looks for the test objects either on `window` or `global`, however it looks like this isn't enough to pick up Jest which isn't published on either.

These changes simplify the setup by looking up the value globally and disabling the type checkng error with `@ts-ignore`. We can't use `declare const` for it, because it causes issues in g3.

I've also reverted some of the `any` types that had to be added in #23636.

Fixes #23365.

(cherry picked from commit ff7fd48)

… defined (#23868)

It is initialized in the contructor, so there is no chance of it being
undefined.

(cherry picked from commit 72d2e5a)

)

The position of the outline gap depends on the size of the prefix, but we weren't set up to update it when that happens.

Fixes #23863.

(cherry picked from commit a6d4141)

We had some workarounds with `HostListener` and `HostBinding` which go against our conventions. They were used to support ViewEngine, but they are no longer necessary.

(cherry picked from commit 5fb821f)

… fix (#23922)

Updates to Karma v6.3.8 which contains a sourcemap fix we landed
upstream. Previous versions of Karma printed/polluted the log output
when an error is thrown due to generated-code being part of stack
traces (due to ESBuild downleveling).

More details here:
https://gist.github.com/devversion/549d25915c2dc98a8896ba4408a1e27c.

karma-runner/karma@4f23b14
(cherry picked from commit f69cf6c)

The `tabindex="-1"` on the host node was causing VoicerOver to read out the slide toggle as a group and to read out the label twice. These changes remove the `tabindex` like we've done for `mat-radio` and `mat-checkbox` in the past.

(cherry picked from commit b533e61)

…23828)

Currently the single-selection chip shows that it's selected by changing its background color, but that doesn't work in high contrast mode. These changes add a thicker outline when the chip is selected.

(cherry picked from commit 2c637d3)

…onChange constructor (#23735)

(cherry picked from commit 1267263)

…related to verifying environment (#23944)

Update to the latest package which properly checks if the running version of ng-dev is the version
described in yarn lock.

(cherry picked from commit ca18e2d)

…lation output (#23951)

Updates to Angular v13.0.1 which fixes the partial compilation output
for `forwardRef` usages in queries. The fixed partial compilation output
will ensure that Angular CDK/Material works with JIT linking at runtime,
as done in e.g. Jest.

Fix upstream: angular/angular#44113.

We will add some testing for the JIT linker to the `angular/components`
repository with: #23882. That
should help ensuring JIT linking does not regress.

Fixes #23907.

(cherry picked from commit 8cb0f12)