feat: Create job action (#12174 and #4116)

[reggie-k]

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

Closes #12174
Closes #4116

[bygui86]

@reggie-k amazing!! great job!!

@crenshaw-dev and @reggie-k so with this feature we can trigger a Job from a CronJob even without a custom action and the corresponding Lua script, did I get correctly?

[crenshaw-dev]

@bygui86 correct, the action will be bundled with Argo CD.

[reggie-k]

There is now a new built in custom action, called "create-job", that can be invoked on a CronJob resource in the UI.

[jsoref]

Filed #14776 to improve the ux