Release process should be idempotent and re-runnable

[oseoin]

Is your feature request related to a problem? Please describe.
Currently the release process only runs on a tag, which makes re-running in the case of issues difficult.

Describe the solution you'd like
Release pipeline can be manually triggered for a specific tag and repeated if needed.

Describe alternatives you've considered
N/A

Additional context
N/A

Related:
#4891
#4890

### Tasks
- [x] Spike on potential pipeline design
- [x] Bumping version in repo/docs
- [ ] https://github.com/nginxinc/kubernetes-ingress/issues/4965
- [ ] https://github.com/nginxinc/kubernetes-ingress/issues/4963
- [ ] https://github.com/nginxinc/kubernetes-ingress/issues/4964
- [ ] https://github.com/nginxinc/kubernetes-ingress/issues/4966
- [x] Create workflow for release branch creation in release repo
- [x] Create workflow for tagging release in release repo
- [ ] https://github.com/nginxinc/kubernetes-ingress/issues/4967
- [ ] https://github.com/nginxinc/kubernetes-ingress/issues/5134

[github-actions]

Hi @oseoin thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[github-actions]

This issue was closed because it has been stalled for 10 days with no activity.