Add RESTRICTED_PATH to bazel invocations

The bazel command should not be using PATH of the user's environment,
but instead the same RESTRICTED_PATH used in the action environment. In
action execution, this made no difference, but may make a difference for
the workspace status script.

It also makes a difference for bazelisk integration.

Bug: 283971340
Test: Treehugger
Change-Id: I78798e120acd45df7cfe75f7775e9e0a2b9d7fb3
1 file changed
tree: 046486a7657c198164a7dfe2b886764d27ff4335
  1. api_surfaces/
  2. bin/
  3. ci/
  4. compliance/
  5. docs/
  6. examples/
  7. flags/
  8. json_module_graph/
  9. mk2rbc/
  10. mkcompare/
  11. platforms/
  12. product_config/
  13. product_variables/
  14. rules/
  15. scripts/
  16. tests/
  17. utils/
  18. vendor/
  19. .gitignore
  20. bazel.BUILD
  21. bazel.WORKSPACE
  22. buildifier_hook.sh
  23. common.bazelrc
  24. constants_exported_to_soong.bzl
  25. darwin.bazelrc
  26. linux.bazelrc
  27. OWNERS
  28. PREUPLOAD.cfg
  29. README.md
README.md

Bazel

The code in this directory is experimental. Bazel support for Android Platform is undergoing active development and workflow stability is currently not guaranteed.