code-insider change the PATH env every day invalidating bazel cache

[bhack]

• VSCode Version: 1.68-0 insider
• Local OS Version: Ubuntu 20.04
• Local chip architecture: x86
• Reproduces in: Both
• Name of Dev Container Definition with Issue:
  https://github.com/microsoft/vscode-dev-containers/tree/main/repository-containers/github.com/tensorflow/tensorflow/.devcontainer + many other containers that rely on bazel with the PATH in the --actin_env.

Steps to Reproduce:

1. Build a project with bazel inside a container
2. Install a new vscode sider version
3. The PATH env is alterated every day with the (nightly hash) e.h. PATH=/vscode/vscode-server-insiders/bin/linux-x64/<daily-sha>-insider/bin/remote-cli
4. This is going do invalidate the whole project cache and it requires to rebuild large programs from scratch every day after a code-insider update as many projects use PATH env in --action_env:
   https://docs.bazel.build/versions/4.1.0/remote-caching.html#known-issues

Environment variables leaking into an action
An action definition contains environment variables. This can be a problem for sharing remote cache hits across machines. For example, environments with different $PATH variables won’t share cache hits. Only environment variables explicitly whitelisted via --action_env are included in an action definition. Bazel’s Debian/Ubuntu package used to install /etc/bazel.bazelrc with a whitelist of environment variables including $PATH. If you are getting fewer cache hits than expected, check that your environment doesn’t have an old /etc/bazel.bazelrc file.

[bhack]

P.s. It is not only for code-insider it is reproducible also every VsCode stable release as the sha in the PATH it also used for stable releases.

Please migrate this ticket to https://github.com/microsoft/vscode-remote-release if it fits better.

[bhack]

I don't know if we could handle also this with the May plan as it has already some activity on the PATH env handling:
microsoft/vscode-remote-release#6625 (comment) /cc @aeschli

[bhack]

Another side effect is that with the same devcontainer image we will have two incompatible caches running the container from Vscode and using docker run from the terminal as the two PATH envs will not match

[bhack]

I've moved this ticket to microsoft/vscode-remote-release#6746