build: upgrade angular build, integration/bazel and @angular/bazel package to rule_nodejs 2.2.0

[gregmagolan]

Updates to rules_nodejs 2.2.0. This is the first major release in 7 months and includes a number of features as well
as breaking changes.

Release notes:
https://github.com/bazelbuild/rules_nodejs/releases/tag/2.0.0
https://github.com/bazelbuild/rules_nodejs/releases/tag/2.0.1
https://github.com/bazelbuild/rules_nodejs/releases/tag/2.0.2
https://github.com/bazelbuild/rules_nodejs/releases/tag/2.2.0

Features of note for angular/angular:

• stdout/stderr/exit code capture; this could be potentially be useful

• TypeScript (ts_project); a simpler tsc rule that ts_library that can be used in the repo where ts_library is too
  heavy weight

Breaking changes of note for angular/angular:

• loading custom rules from npm packages: ts_library is no longer loaded from @npm_bazel_typescript//:index.bzl
  (which no longer exists) but is now loaded from @npm//@bazel/typescript:index.bzl

• with the loading changes above, load("@npm//:install_bazel_dependencies.bzl", "install_bazel_dependencies") is
  no longer needed in the WORKSPACE which also means that yarn_install does not need to run unless building/testing
  a target that depends on @npm. In angular/angular this is a minor improvement as almost everything depends on @npm.

• @angular/bazel package is also updated in this PR to support the new load location; Angular + Bazel users that
  require it for ng_package (ng_module is no longer needed in OSS with Angular 10) will need to load from
  @npm//@angular/bazel:index.bzl. I investigated if it was possible to maintain backward compatability for the old
  load location @npm_angular_bazel but it is not since the package itself needs to be updated to load from
  @npm//@bazel/typescript:index.bzl instead of @npm_bazel_typescript//:index.bzl as it depends on ts_library
  internals for ng_module.

• runfiles.resolve will now throw instead of returning undefined to match behavior of node require

Other changes in angular/angular:

• integration/bazel has been updated to to use both ng_module and ts_libary with use_angular_plugin=true.
  This latter is the recommended way for rules_nodejs users to compile Angular 10 with Ivy. Bazel + Angular ViewEngine is
  supported with @angular/bazel <= 9.0.5 and Angular <= 8. There is still Angular ViewEngine example on rules_nodejs
  https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular_view_engine on these older versions but users
  that want to update to Angular 10 and are on Bazel must switch to Ivy and at that point ts_library with
  use_angular_plugin=true is more performant that ng_module. Angular example in rules_nodejs is configured this way
  as well: https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular. As an aside, we also have an
  example of building Angular 10 with architect() rule directly instead of using ts_library with angular plugin:
  https://github.com/bazelbuild/rules_nodejs/tree/stable/examples/angular_bazel_architect.

NB: ng_module is still required for angular/angular repository as it still builds ViewEngine & @angular/bazel
also provides the ng_package rule. ng_module can be removed in the future if ViewEngine is no longer needed in
angular repo.

• JSModuleInfo provider added to ng_module. this is for forward compat for future rules_nodejs versions.
  @josephperrott, this touches packages/bazel/src/external.bzl which will make the sync to g3 non-trivial.

[jbedard]

@angular/bazel/src/external.bzl also needs a minor change:

--- a/node_modules/@angular/bazel/src/external.bzl
+++ b/node_modules/@angular/bazel/src/external.bzl
@@ -2,11 +2,11 @@
 """
 
 load(
-    "@npm_bazel_typescript//internal:build_defs.bzl",
+    "@npm//@bazel/typescript/internal:build_defs.bzl",
     _tsc_wrapped_tsconfig = "tsc_wrapped_tsconfig",
 )
 load(
-    "@npm_bazel_typescript//internal:common/compilation.bzl",
+    "@npm//@bazel/typescript/internal:common/compilation.bzl",
     _COMMON_ATTRIBUTES = "COMMON_ATTRIBUTES",
     _COMMON_OUTPUTS = "COMMON_OUTPUTS",
     _DEPS_ASPECTS = "DEPS_ASPECTS",
@@ -14,7 +14,7 @@ load(
     _ts_providers_dict_to_struct = "ts_providers_dict_to_struct",
 )
 load(
-    "@npm_bazel_typescript//internal:ts_config.bzl",
+    "@npm//@bazel/typescript/internal:ts_config.bzl",
     _TsConfigInfo = "TsConfigInfo",
 )
 load(

[alexeagle]

🦸‍♀️

[petebacondarwin]

@gregmagolan - could you make this PR "draft" so that it doesn't trigger review request from lots of the team?

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     status "cla/google" is failing
     status "ci/circleci: test" is pending
     status "google3" is pending
     missing required status "ci/circleci: publish_snapshot"
     1 pending code review

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[googlebot]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}