ci: change bazel to use XL container resources

We are limiting Bazel to consuming resources that fit in CircleCI "medium" class but Circle steps are configured to use "xlarge" containers

https://github.com/angular/angular-cli/blob/aacb98d85bac837b898dc6158459aef53f5569a3/.circleci/bazel.rc#L13-L17

Changing the contain to "medium" causes `Stream closed` failures

Author: alan-agius4

.circleci/bazel.rc

@@ -12,10 +12,10 @@ test --test_tag_filters=-manual
 
 # Workaround https://github.com/bazelbuild/bazel/issues/3645
 # Bazel doesn't calculate the memory ceiling correctly when running under Docker.
-# Limit Bazel to consuming resources that fit in CircleCI "medium" class which is the default:
+# Limit Bazel to consuming resources that fit in CircleCI "xlarge" class
 # https://circleci.com/docs/2.0/configuration-reference/#resource_class
-build --local_ram_resources=3072
-build --local_cpu_resources=2
+build --local_cpu_resources=8
+build --local_ram_resources=14336
 
 # More details on failures
 build --verbose_failures=true

.circleci/config.yml

@@ -260,6 +260,7 @@ jobs:
     steps:
       - custom_attach_workspace
       - install_python
+      - run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc
       - run: 
           command: yarn bazel:integration
           no_output_timeout: 20m