Releases automation proposal

[VannTen]

Here's the proposal to have a less manual release workflow:

• Create a changelogs directory
• Change the release process to use PR instead of issues, and create a file (Filename == release ? TODO) for each release which will become the content of the release notes. -> this allows us to leverage /lgtm and /approve.
• Use a github worklow to create release from the merged file (https://github.com/marketplace/actions/create-a-release-in-a-github-action) for instance.
• Possibly other parts, like pushing the relevant images ....

Follow-ups:

• automate the PR (but we'll probably run into Update kubernetes-client organization to allow Github Actions to create pull requests kubernetes/org#5126
• add artifacts (ansible collection ...)

@yankay @tico88612 wdyt ?

[yankay]

I fully support the idea of release automation and think the proposal is excellent.

Additionally, I think we could also take inspiration from the approaches used by other Kubernetes subprojects, for example:

https://github.com/kubernetes-sigs/kueue/blob/main/RELEASE.md