Allow --experimental_remote_cache_compression to be used as common option

[keith]

If you'd like to always enable --experimental_remote_cache_compression it's natural to put it in your .bazelrc as:

common --experimental_remote_cache_compression

But this ends up breaking commands that don't support this flag:

% bazel help
INFO: Reading rc options for 'help' from .../.bazelrc:
  Inherited 'common' options: --experimental_remote_cache_compression
ERROR: --experimental_remote_cache_compression :: Unrecognized option: --experimental_remote_cache_compression

It would be great if this flag was ignored instead as others such as --experimental_downloader_config are.

What's the output of bazel info release?

release 5.0.0

[larsrc-google]

Does this flag have any effect outside of build commands (and their derivatives like test etc)? If not, put it in your .bazelrc as build --experimental_remote_cache_compression.

[keith]

It is mentioned in the docs that it's also compatible with query, although I'm not sure how much that matters, but I think practically for flags like this, there should be some consistent way users can say "apply this all the time!" without having to know exactly which commands it affects. I imagine most folks just throw everything under build, but that can be risky depending on the flag #10961

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[tjgq]

I believe this has been addressed by #18130.