[FLINK-26331] Make cleanup retry strategy configurable similar to how the task restart is configurable

[XComp]

What is the purpose of the change

The goal is to align the user experience for retry functionality. I created a follow-up ticket FLINK-26359 to cover the actual alignment in the code.

Brief change log

• Introduced CleanupOptions similar to RestartOptions to give a consistent user experience.
• Adds CleanupRetryStrategyFactory covering the configuration extraction to create the right RetryStrategy instance
• Updated docs

Verifying this change

• CleanupRetryStrategyFactoryTest is added to cover all different options

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): yes
• 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: yes
• The S3 file system connector: no

Documentation

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

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit a2dec76 (Thu Feb 24 18:44:30 UTC 2022)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[flinkbot]

CI report:

• 217a4a0 Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

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

[XComp]

The compiled docs look like that:

[autophagy]

A few small documentation suggestions, and just a comment so I better understand what the enum factory pattern is for - but otherwise lgtm!

[XComp]

Thanks @autophagy for your review. I applied your comments, squashed the commits and rebased the branch. I will merge it after the final CI run succeeds.

[XComp]

Test failure unrelated to changes: FLINK-26387 I'm going to merge the PR