build: use bazel version from node modules (#26691)

* No longer depends on a custom CircleCI docker image that comes with Bazel pre-installed. Since Bazel is now available through NPM, we should be able to use the version from `@bazel/bazel` in order to enforce a consistent environment on CI and locally.
* This also reduces the amount of packages that need to be published (ngcontainer is removed)

PR Close #26691

packages/bazel/index.bzl

@@ -22,4 +22,4 @@ protractor_web_test = _protractor_web_test
 protractor_web_test_suite = _protractor_web_test_suite
 ng_setup_workspace = _ng_setup_workspace
 # DO NOT ADD PUBLIC API without including in the documentation generation
-# Run `bazel build //packages/bazel/docs` to verify
+# Run `yarn bazel build //packages/bazel/docs` to verify

packages/bazel/package.bzl

@@ -87,16 +87,11 @@ def rules_angular_dev_dependencies():
         url = "https://github.com/bazelbuild/bazel/archive/0.18.0.zip",
     )
 
-    # This commit matches the version of buildifier in angular/ngcontainer
-    # If you change this, also check if it matches the version in the angular/ngcontainer
-    # version in /.circleci/config.yml
-    BAZEL_BUILDTOOLS_VERSION = "49a6c199e3fbf5d94534b2771868677d3f9c6de9"
-
     http_archive(
         name = "com_github_bazelbuild_buildtools",
-        sha256 = "edf39af5fc257521e4af4c40829fffe8fba6d0ebff9f4dd69a6f8f1223ae047b",
-        strip_prefix = "buildtools-%s" % BAZEL_BUILDTOOLS_VERSION,
-        url = "https://github.com/bazelbuild/buildtools/archive/%s.zip" % BAZEL_BUILDTOOLS_VERSION,
+        sha256 = "a82d4b353942b10c1535528b02bff261d020827c9c57e112569eddcb1c93d7f6",
+        strip_prefix = "buildtools-0.17.2",
+        url = "https://github.com/bazelbuild/buildtools/archive/0.17.2.zip",
     )
 
     #############################################

packages/bazel/test/ng_package/example_package.spec.ts

@@ -101,7 +101,7 @@ function runPackageGoldTest(testPackage: TestPackage) {
           `    Diff:\n` +
           `    ${patch}\n\n` +
           `    To accept the new golden file, run:\n` +
-          `      bazel run ${process.env['BAZEL_TARGET']}.accept\n`;
+          `      yarn bazel run ${process.env['BAZEL_TARGET']}.accept\n`;
 
       fail(failureMessage);
     }

packages/compiler-cli/src/ngcc/README.md

@@ -10,7 +10,7 @@ This conversion will allow such "legacy" packages to be used by the Ivy renderin
 The project is built using Bazel:
 
 ```bash
-bazel build //packages/compiler-cli/src/ngcc
+yarn bazel build //packages/compiler-cli/src/ngcc
 ```
 
 ## Unit Testing
@@ -18,7 +18,7 @@ bazel build //packages/compiler-cli/src/ngcc
 The unit tests are built and run using Bazel:
 
 ```bash
-bazel test //packages/compiler-cli/src/ngcc/test
+yarn bazel test //packages/compiler-cli/src/ngcc/test
 ```
 
 ## Integration Testing
@@ -26,5 +26,5 @@ bazel test //packages/compiler-cli/src/ngcc/test
 There are tests that check the behaviour of the overall executable:
 
 ```bash
-bazel test //packages/compiler-cli/test/ngcc
+yarn bazel test //packages/compiler-cli/test/ngcc
 ```

packages/compiler-cli/test/compliance/README.md

@@ -1,3 +1,5 @@
 Tests in this directory should be run with:
 
-bazel test --define=compile=aot  packages/compiler-cli/test/compliance:compliance
+```
+yarn bazel test --define=compile=aot  packages/compiler-cli/test/compliance:compliance
+```