build: run snapshot local browser tests with bazel (#16832)

Runs the snapshot local browser tests with Bazel. This improves
our consistency and allows us to remove `gulp test` in the future.

(cherry picked from commit 9661530)

Author: devversion

.circleci/config.yml

@@ -388,19 +388,19 @@ jobs:
   snapshot_tests_local_browsers:
     docker: *docker-firefox-image
     resource_class: xlarge
+    environment:
+      GCP_DECRYPT_TOKEN: *gcp_decrypt_token
     steps:
     - *checkout_code
     - *restore_cache
+    - *setup_bazel_ci_config
+    - *setup_bazel_remote_execution
     - *yarn_download
     - *yarn_install
+    - *setup_bazel_binary
 
     - run: node ./scripts/circleci/setup-angular-snapshots.js --tag master
-      # We need to re-run yarn install in order to pull the Angular snapshot builds. Note
-      # that we can't use the "--frozen-lockfile" option since the setup snapshots script does
-      # not update the lock file.
-    - run: yarn install --non-interactive
-    - run: ./scripts/circleci/run-local-browser-tests.sh
-
+    - run: bazel test src/... --build_tag_filters=-e2e --test_tag_filters=-e2e
 
   # ----------------------------------------------------------------------------
   # Job that runs all Bazel tests against Ivy with the current Angular version

angular-tsconfig.json

@@ -2,6 +2,11 @@
 // This file is required because when using the Angular NPM packages and building
 // with AOT compilation, NGC needs the "ngsummary.json" files.
 {
+  "angularCompilerOptions": {
+    // In snapshot builds the compiler-cli will now use ngtsc by default. In
+    // order to be able to build the summary files, we need to use ngc.
+    "enableIvy": false
+  },
   "compilerOptions": {
     "module": "umd",
     "moduleResolution": "node",