Remote file write

### Description of the feature request:

A way to configure write actions to only write results to the remote cache.

### Which category does this issue belong to?

_No response_

### What underlying problem are you trying to solve with this feature?

Currently, when building or testing a large number of targets with a spawn_strategy set to remote, there can still be a significant amount of work put on the disk of the bazel client. All FileWrite actions (based on my read of the code, happy to be corrected here) execute locally, and the results are then uploaded to cache as needed.

This means if I try to test a large number of remote targets, I still need to locally generate and hold all FileWrite action results, even if none of them will ever be read locally. This greatly increases the disk requirements of the bazel client. This can be somewhat cut down with flags like --nobuild_runfile_manifests, but it'd be nice to still generate this content without having to hold it locally.

### Which operating system are you running Bazel on?

Linux

### What is the output of `bazel info release`?

release 7.4.1

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

_No response_

### Have you found anything relevant by searching the web?

Testing remotely with --nobuild_runfile_manifests technically doesn't work right now, but this seems to be known https://github.com/bazelbuild/bazel/issues/23980

### Any other information, logs, or outputs that you want to share?

Very thankful for this project, and your work on it this far, and I'm happy to be corrected if I'm way off-base on anything here.