Batch delete requests for exchange spooling on S3 and Azure

[linzebing]

Description

Is this change a fix, improvement, new feature, refactoring, or other?

Improvement.

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

trino-filesystem-exchange

How would you describe this change to a non-technical end user or system administrator?

This will help reduce the number of delete request sent to S3/Azure by batching them.

Related issues, pull requests, and links

Depend on #12360

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

[losipiuk]

errorprone:

Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.9.0:compile (default-compile) on project trino-exchange-filesystem: Compilation failure
Error:  /home/runner/work/trino/trino/plugin/trino-exchange-filesystem/src/main/java/io/trino/plugin/exchange/filesystem/azure/AzureBlobFileSystemExchangeStorage.java:[270,63] [UnusedVariable] The parameter 'containerName' is never read.
Error:      (see https://errorprone.info/bugpattern/UnusedVariable)
Error:    Did you mean 'return deleteObjects(blobUrls.build());'?
Error:  -> [Help 1]

[losipiuk]

LGTM

[arhimondr]

I wonder if it is possible to give this method a better name. How about calling the method translateFailures? (I know that it also transforms the future into a ListenableFuture<Void> future, but that's probably a less important aspect of it that can be safely omitted without significantly decreasing readability )

[arhimondr]

nit: Generally we are trying to avoid *Util classes as they tend to end up being a dump site of a bunch of loosely related hardly reusable code. I would recommend calling it FileSystemExchangeFutures. It will make it more obvious of what methods this class may contain and potentially increase the likelihood of the methods being used / reused.

[linzebing]

CI: #12535

[losipiuk]

commit message typo sppoling