Update bazelrc with some bazel 5.0 cache flags

[bduffany]

This will give us some experience using these flags, since we are recommending them with the suggestions cards.

• Enable --experimental_remote_cache_compression when running with --config=remote or --config=cache (does not apply to workflows since it's likely to be detrimental, and not to github CI either since it's unclear whether the network is a bottleneck there)
• Enable --experimental_remote_cache_async and --incompatible_remote_build_event_upload_respect_no_cache unconditionally

---

Version bump: Patch

[vadimberezniker]

It looks like --incompatible_remote_build_event_upload_respect_no_cache also prevents logs from being uploaded when --noremote_upload_local_results is set. Is that intentional? I use --noremote_upload_local_results in my user bazelrc.

[brentleyjones]

I believe so: bazelbuild/bazel#14338 (comment)

test logs are treated as action outputs. i.e. they are uploaded if the result of test actions can be uploaded. Or not uploaded if tagged with "no-cache".

[bduffany]

Seems a bit unfortunate that the only way to upload test logs is to disable --noremote_upload_local_results, which I guess may upload a bunch of other unwanted stuff?

[brentleyjones]

Correct. It's probably worth a Bazel GitHub issue.