Dagger caching settings cause shutdown timeout

[tender pier]

I've been experimenting with s3 caching and ran into this issue.
Turns out it's not new, and there is even a ticket for it: https://github.com/dagger/dagger/issues/11328.

In my experiments caching seems pretty effective, and if it wasn't for this timeout failure would make selling dagger to other teams a lot easier.

I created a PR https://github.com/dagger/dagger/pull/11585, which would help address the problem. It simply introduces yet another EXPERIMENTAL_... variable for shutdown timeout, so it's a safe change.

It'd be very nice to see a fix in the next release, whether it's this or something else.

[rain cove]

thx for the contribution! 🙏 Left a nit comment and requested a review from some other maintainer

[tender pier]

thx for the quick response, I see other 3 constants defined later in the same file, not a the top.
I could move the const block to the top and also add _EXPERIMENTAL_DAGGER_CHECKS_SCALE_OUT while at it.

[rain cove]

👍 sweet, thx