Improve Kubeflow Trainer 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.
• Publish Kubeflow Trainer modules to PyPI

/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

[tenzen-y]

Additionally, I would like to use the semantic versioning image tags every for the release here: https://github.com/kubeflow/training-operator/blob/f8687ca7fd947e6ebd52dde4dfeefdf006e7b239/manifests/overlays/standalone/kustomization.yaml#L9

[7h3-3mp7y-m4n]

okay I'll look at it and raise a PR ASAP

[Deathfireofdoom]

No one is working on this one right? I can take a look
/assign

[tenzen-y]

No one is working on this one right? I can take a look /assign

Yes, feel free to take this.

[andreyvelich]

Thank you for your time @Deathfireofdoom!
I would also suggest to also check how we refactor and automate the Spark Operator release process with @ChenYi015 : kubeflow/spark-operator#2089

I think, we can re-use some of the steps.