Update release process docs

[damdo]

Here are a few things we picked up while going through the release process:

• Add kpromo step instead of cip-mm
• Add step for announcing the release (slack + google group list email), maybe similarly to https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/docs/book/src/development/releasing.md#verify-and-publish-the-draft-release
• Add step to update the periodics/presubmit jobs in case of a new minor release

Feel free to add more if there was something else you wanted to add: cc. @cpanato @salasberryfin

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[damdo]

Still like to get to this

/remove-lifecycle stale