feat: add CRD property for retry on failure

[razvan]

Description

See #646

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

• Changes are OpenShift compatible
• CRD changes approved
• CRD documentation for all fields, following the style guide.
• Helm chart can be installed and deployed operator works
• Integration tests passed (for non trivial changes)
• Changes need to be "offline" compatible
• Links to generated (nightly) docs added
• Release note snippet added

Reviewer

• Code contains useful comments
• Code contains useful logging statements
• (Integration-)Test cases added
• Documentation added or updated. Follows the style guide.
• Changelog updated
• Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

• Feature Tracker has been updated
• Proper release label has been added
• Links to generated (nightly) docs added
• Release note snippet added
• Add type/deprecation label & add to the deprecation schedule
• Add type/experimental label & add to the experimental features tracker

[sbernauer]

I think I would rename the PR to something like feat: Support configuring number of retries on failure, as it now has evolved

[sbernauer]

Please wait with merging till the decision was accepted

[razvan]

Release note

Starting with this version, Spark applications will not be resubmitted automatically in case of failure.
Users can restore the previous behavior by setting the new spec.job.retryOnFailureCount property to a non negative value.

In addition, small improvements have been made to clean up resources created by Spark applications.

• application driver pods are now deleted as soon as they reach a terminal state.
• application executor pods are now deleted as soon as possible in case of driver or submit failure.