feat(bazel): allow passing and rewriting an old bazel host #31381
Updates the decision made in #31341; this is for the Angular indexer
Please check if your PR fulfills the following requirements:
What kind of change does this PR introduce?
What is the current behavior?
The indexer currently passes (and ngc-wrapped#compile accepts) a bazel host to use.
What is the new behavior?
Does this PR introduce a breaking change?
This breaks the Angular indexer inside Google. Is it highly unlikely that anyone is using this API. Migration plan is to change the