Improve Training Operator release process

[andreyvelich]

Related: kubeflow/katib#2049

We need to improve our release process for Training Operator:

• Branch names should follow this pattern: release-X.Y. Similar to Katib or Kubernetes.
• Automate release with GitHub Actions.

/good-first-issue
/help

[google-oss-prow]

@andreyvelich:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Related: kubeflow/katib#2049

We need to improve our release process for Training Operator:

• Branch names should follow this pattern: release-X.Y. Similar to Katib or Kubernetes.
• Automate release with GitHub Actions.

/good-first-issue
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[7h3-3mp7y-m4n]

I want to take this.
/assign