refactor: support PnP for experimental package and MDC deps

Yarn PnP requires explicit listing of dependencies used. Since our
Sass files/compilations do not use `material-components-web` but
rather use the individual `@material/<..>` packages, we need to switch
away from the kitchen-sink package.

As part of this, we have two options long-term:

* Add all individual deps as peer dependencies
* Add all individual deps as _direct_ dependencies.

The latter seems more convenient for users and we also cannot
make any guarantees that a more recent "build" of the `@material/<..>`
packages is still compatible. If users would intend to force a more
recent MDC version, they could still use a Yarn resolution, or we could
also bump our `dependencies` using a `caret` or `tilde` (once we are relying
on a rather stable version of MDC -- that is a potential option then)

Author: devversion

integration/yarn-pnp-compat/BUILD.bazel

@@ -1,4 +1,15 @@
+load("@bazel_skylib//lib:dicts.bzl", "dicts")
 load("//tools:defaults.bzl", "node_integration_test")
+load("//tools:integration.bzl", "CLI_PROJECT_MAPPINGS")
+
+npmPackageMappings = dicts.add(
+    CLI_PROJECT_MAPPINGS,
+    {
+        "//src/cdk:npm_package_archive": "@angular/cdk",
+        "//src/material:npm_package_archive": "@angular/material",
+        "//src/material-experimental:npm_package_archive": "@angular/material-experimental",
+    },
+)
 
 node_integration_test(
     name = "test",
@@ -14,10 +25,7 @@ node_integration_test(
         # Set `CI` to silence `yarn berry` and make the output readable.
         "CI": "true",
     },
-    npm_packages = {
-        "//src/cdk:npm_package_archive": "@angular/cdk",
-        "//src/material:npm_package_archive": "@angular/material",
-    },
+    npm_packages = npmPackageMappings,
     tags = [
         # This test relies on `yarn` so there needs to be internet access.
         "requires-network",