Release of `v20.0.1`

[frouioui]

[!NOTE]
This release is scheduled for Thu 20 Jun 2024. The release of vitess-operator v2.13.0 is also planned. Release team: @vitessio/release

[!IMPORTANT]
Please do not edit the content of the Issue's body manually. The vitess-releaser tool is managing and handling this issue. You can however click on the check boxes to mark them as done/not done, and write comments.

Prerequisites (~2 weeks before)

• [ ] General prerequisites.
  • [ ] Be part of the Release team in the vitessio GitHub organization, here.
  • [ ] Be an admin of the planetscale/vitess-operator repository.
  • [ ] Have access to Vitess' Java repository and have it working locally, guide here.
  • [ ] Have vitessio/vitess and planetscale/vitess-operator cloned in the same parent directory.
• [ ] Notify the community on Slack.
• [ ] Make sure the release notes summary is prepared and clean.
• Make sure important Pull Requests are merged, list below.
  • [ ] #361
  • [ ] #357
• Make sure release blocker items are closed, list below.

  Code Freeze (~1-3 days before)

• [ ] Code Freeze.
• [ ] Create new GitHub Milestone.

Pre-Release (~1-3 days before)

• [ ] Create Release PR. _{^{(We do this earlier to catch any issues in the tool and let CI run.)}}
• [x] Update vitess-operator Golang version.
  • https://github.com/frouioui/vitess-operator/pull/26

Release (Thu 20 Jun)

• [ ] Merge the Release PR.
• [ ] Tag the release.
• [ ] Create vitess-operator Release PR.
• [ ] Manual update of vitess-operator test code.
• [ ] Update release notes on main.
• [ ] Go back to dev mode on the release branch.
• [ ] Update the website documentation.
• [ ] Make sure the release is benchmarked by arewefastyet.
• [ ] Docker Images available on DockerHub.
• [ ] Close current GitHub Milestone.

Post-Release (Thu 20 Jun)

• [ ] Notify the community on Slack for the new release.
• [ ] Twitter announcement.
• [ ] Close this Issue.