run e2e legacy tests under bazel

[jbedard]

This runs the legacy-cli/e2e tests via bazel using the bazel built npm packages from packages/**.

After all the pre-factors it's mainly just build config and a few code changes to use the bazel environment vars if present. This can be simplified if the non-bazel versions are dropped in the future. Currently all the CI jobs are prefixed with bazel-.

Build targets / API:

There are 9 bazel targets invoking the e2e tests with different configurations:

• //tests/legacy-cli:e2e.{npm,yarn,esbuild,saucelabs}: configured like CI today
• //tests/legacy-cli:e2e.snapshot.{npm,yarn,esbuild,saucelabs}: ^ using snapshots
• //tests/legacy-cli:e2e: nothing pre-configured, does not run by default or on CI, is designed to be run and configured manually with bazel cli args.

With any of these you can:

• bazel test to run as a bazel test
• bazel run to do the equivalent of --debug and remain running on failure
• --test_filters="..." which essentially does the e2e_runner --glob="..."
• --test_arg="..." to specify additional e2e_runner args, --glob would work here too

Sharding
Today e2e tests have --shard and --nb-shards cli params which circleci sets based on the parallelism config.
Now those cli args are defaulted based on the bazel environment variables set by nodejs_test(shard_count) and/or the E2E_SHARD_TOTAL + E2E_SHARD environment variables I added. This way both bazel and circleci sharding can be combined into one (bazel shards via processes on one circleci environment, circleci sharding in isolated environments).

Prefactors:

• test: fix ts compiler errors #23130
• test: use random ports for local verdaccio npm servers #23114
• test: remove use of global npm cache and config  #23115
• run e2e tests in isolated child processes #23245
• test: use dynamic ports for e2e tests #23313
• test: do not depend on a global npm binary #23326
• use private yarn pkg cache, ensure private npm/yarn bin always on path #23372
• test: remove exclusion of bazel tests based on manual tag #23640
• test: use random e2e test ports #23541
• test: revert local test project file changes on test completion #23648
• test: move tempdir creation to util method #23649
• test: use common mockHome method #23687
• test: improve test error message logs #23694
• test: add missing yargs config #23711
• test: ensure test assets are writable when copied for use in e2e tests #23712
• test: remove ci specific logic #23686
• test: watch full stdout when waiting for match #23767
• test: unit test multiple node versions in separate jobs #23714
• test: run e2e tests on pre-compiled packages #23753
• test: suppress npm update warnings #23902
• test: catch and log all errors include test setup #23903
• test: enable git core.longpaths option #23926

[josephperrott]

LGTM though still other comments that appear to be unaddressed.

[jbedard]

I think those were all addressed offline and not in the comments here, just no one had pressed resolve.

[alan-agius4]

One comment otherwise LGTM. Can you also squash please?

[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.}