feat(controller): Workflow-level retryStrategy/resubmit pending pods by default. Closes #3918

[alexec]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed the CLA.
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

Closes #3918
Related to ##2385

Changes

• Support retryStrategy at workflow level.
• Completely remove resubmitPendingPods and always resubmit them.

[alexec]

FAIL: TestFunctionalSuite/TestRetryStrategy 

[alexec]

FAIL: TestArgoServerSuite/TestWorkflowService/Terminate
FAIL: TestArgoServerSuite/TestWorkflowService/Resubmit
FAIL: TestCLIWithServerSuite/TestNodeSuspendResume

[alexec]

FAIL: TestFunctionalSuite/TestDeletingRunningPodWithOrErrorRetryPolicy (39.99s)

[jamesgunnfiveai]

Hi folks - we've just bumped into a problem where some users with clients on 2.12.x can't parse our workflows that contain resubmitPendingPods: true whereas 2.11.x clients can. I believe this is a result of this MR removing the field in versions >=2.12 (this is solved by just having them downgrade to 2.11.x for now). Just curious whether it was intentional that this landed in a minor version bump as I would have thought it should be major according to semver.