[FLINK-39135] [flink-gs-fs-hadoop] Set proper precondition to ensure GCS operations are retryable

[jonchase]

What is the purpose of the change

Ensures that the operations become idempotent or atomic, allowing the GCS client to safely retry the 503 errors. Thus client can actually perform the retry in such conditions.

Original retry logic was added in #24753.

It was then added to the compose operation in #27101. This PR cherry picks that PR into the 1.20 release branch.

Brief change log

• Adds an option when composing the GCS request, to ensure that operation is atomic
• Adds an option when writing to GCS, to ensure that write operation is atomic

Verifying this change

This change is already covered by existing tests, such as GSRecoverableWriterTest

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

CI report:

• 7ae5472 Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build