feat: Allow to change priority when resubmitting workflows

[terrytangyuan]

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.

[simster7]

We don't need this here if we use priority *int32 instead of priority int32. Take a look at commands/submit.go.

Can you refactor this to match?

[terrytangyuan]

Thanks. Just updated.

[terrytangyuan]

Something seems wrong in the build as it’s stuck in “wait for Argo Server to be ready”. Any clues @simster7?

[simster7]

Are you able to run make start locally?

[terrytangyuan]

@simster7 I had to revert my last change so the argo server can start successfully. It was actually already following the same behavior as in commands/submit.go. Did I miss anything?

Edit: codegen build failure is unrelated and is also happening on master branch.

[alexec]

This bug that broke your build is fixed on master - you'll need to sync with master to get green and merged.

[terrytangyuan]

@alexec Thanks. Just rebased and it's green now.