fix: fix execution requirements for 'build without the bytes'

[gregmagolan]

With "build without the bytes" working correctly and default in Bazel 7, our copy execution requirements should allow caching so that it works with this mode out of the box.

We should also not be opinionated about remote execution since with "build without the bytes", if you're copying all generated files around then it may be more efficient to do it on a remote executor. The subset of users that use remote execution can easily set custom execution requirements for the Mnenomic if desired.

---

Type of change

• Performance (a code change that improves performance)

Test plan

• Covered by existing test cases

[alexeagle]

We need to discuss this one, as we've gone back and forth several times now.

#594 points to #528 where we learned that some users rely on this.

We now have two modes in bazel-lib 2.0 https://github.com/aspect-build/bazel-lib/blob/main/docs/copy_file.md#choosing-execution-requirements

I don't understand whether your change here is a complete retreat from local performance opt.

[gregmagolan]

It's not a retreat. It keeps the main local development optimization of no-sandbox which is the important one but it adds the ability remote cache the actions so that "build without the bytes" is optimal. It shaves off minutes of copying off of a new clone that is fully cached in a large rules_js repository with "build without the bytes" enabled.

[alexeagle]

Sure but do we understand how this new version satisfies all the problems we had with other attempts at this?

[gregmagolan]

I understand how the requirements of "build without the bytes" fit in now after a deep dive last week. I think we should support that mode by default. Not allowing cacheing & remote execution is the wrong default IMO.

In terms of problems, performance with sandboxing was the big one which is the one default that makes sense to keep. If there was a way to not bother writing to the disk cache but still enable cacheing for the remote cache that would be nice but there is not AFAIK.

[kzadorozhny]

This is a very welcome change. Being able to speed up CopyFile actions is a big win.
For example, the total time spent copying 4K+ ts_priject source files is more than 220 seconds.