`cas: false` not being respected? about bazel-buildfarm

[werkt]

For those watching, /tmp/worker/cache will fill at roughly the same rate with or without storage with the following deltas: the write rate will likely be differentiated from the write rate for the cluster, it will now be proportional to the rate of new input arrivals for action executions, and the outputs for actions that are not used as inputs will not contribute to writes on the worker, as these will all be offloaded to storage workers in the cluster.

The storage expiration will function exactly as before, with the overall write rate determined through input downloads, with removals making space to fit within maxSizeBytes, and maxEntrySizeBytes will be unaffected.

Closing as this answer resolves the behavior and was confirmed OOB. Perhaps documentation could be updated in the future to describe this story in a worker allocation pattern for exec-only and storage worker distinctions.