Remote repo contents cache is known to not work correctly

[aignas]

In our repository we are using remote contents cache metadata in the following repositories:

• whl_library - symlinks from the venv are added to files from this repo if we are using the site-packages venv layout, which is not the default yet.
• uv_repository - it is unaffected
• python_repository - symlinks from the venv are added to files from this repo

https://github.com/search?q=repo%3Abazel-contrib%2Frules_python%20repo_metadata&type=code

Because of how we are using symlinks to create a venv as part of the build actions, there may be failures, like:

ERROR: Python interpreter not found: /home/buildbuddy/workspace/output-base/execroot/_main/bazel-out/k8-fastbuild/bin/libs/artifacts/cli.runfiles/_main/libs/artifacts/_cli.venv/bin/python3

The relevant .bazelrc is:

startup --experimental_remote_repo_contents_cache

A potential workaround is to avoid creating symlinks

common --@rules_python//python/config_settings:venvs_use_declare_symlink=no

Flag documentation