feat(@angular/build): allow enabling Bazel sandbox plugin with esbuild

[sbarfurth]

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

User facing documentation is intentionally omitted as this will be considered internal for now.

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

When trying to integrate the esbuild based builder into Bazel with rules_js we found that it will incorrectly follow symlinks out of the sandbox. This is because Node.js based tooling runs in the output tree to support canonical JS project directory structures. The output tree will contain symlinks outside of the sandbox. Node tooling will generally follow these symlinks, which violates the rules of Bazel sandboxing. This can manifest in a wide variety of errors. One example we encountered with Angular compilation is that the symlinked browser entry point (e.g. main.ts) is outside of the range of tsconfig.json when the compiler follows the symlink.

Issue Number: N/A

What is the new behavior?

Setting the new ENABLE_BAZEL_SANDBOX_PLUGIN environment variable to true or 1 during a build with the esbuild based builder will now inject a special plugin to make esbuild compatible with Bazel builds in the output tree.

Does this PR introduce a breaking change?

• Yes
• No

Other information

The plugin itself was originally written in https://github.com/aspect-build/rules_esbuild. The version container in this commit is a fork of https://github.com/aspect-build/rules_esbuild/blob/e4e49d3354cbf7087c47ac9c5f2e6fe7f5e398d3/esbuild/private/plugins/bazel-sandbox.js. I've adapted the JS file to TypeScript and made no further changes.

[devversion]

For additional context: This will also be useful / needed for our usages of CLI inside Bazel for e.g. angular.dev

[sbarfurth]

I've had to change the original plugin to try for a .js file is a .ts file was resolved but doesn't exist in the sandbox. One example where this happens is if a .ts file is pre-compiled with something like ts_project. The sandbox then only gets the output of ts_project, but the ts_project rule itself depended on the .ts file. This means the .ts file will be present outside the sandbox, but it won't be linked into it. The resolution will resolve the .ts file outside the sandbox, but the path mapped back into the sandbox won't exist. Simply rewriting to .js is sufficient for this case and seems sensible enough.

[sbarfurth]

Should I make any further changes here? Happy to help get this merged if it's something I can support.

[jkrems]

@clydin I assume this is something you're still looking at / want to look at?