🌱 hack: add weekly update script for Slack

[willie-yao]

What this PR does / why we need it:

This is a new PR based mainly off of the work by @oscr in #8192
This PR adds a subcommand weekly to the existing notes.go command that generates the weekly updates that the comms team shares on Slack each week. This will make it simpler to create the messages and less chance of mistakes.

$ go run hack/tools/release/notes.go weekly --since 2023-08-13 --until 2023-08-20 --milestone v1.6

Weekly update :rotating_light:
Changes from 2023-08-13 to 2023-08-20 a total of 44 new commits where merged into main.

- 1 Breaking Changes :warning:
         - Improve Context handling in clusterctl (#8939)

- 5 New Features :sparkles:
         - Add automation to create release branch and tags (#9111)
         - block move with annotation (#8690)
         - machineset: adjust preflight check to allow kubelet version skew of 3 for clusters running v1.28 and above (#9222)
         - v1.28: Prepare quickstart, capd and tests for the new release including kind bump (#9160)
         - Add topology-owned label to MachineHealthChecks. (#9191)

- 5 Bug Fixes :bug:
         - test: pin conformance image to a version which includes a fix for the dualstack tests (#9252)
         - tilt: ensure .tiltbuild/bin directory is created early enough, add tilt troubleshooting guide (#9165)
         - Certificate paths in cloud-init scripts should not use a platform-dependent path separator (#9167)
         - Allow to drop useExperimentalRetryJoin field from KubeadmControlPlane.kubeadmConfigSpec (#9170)
         - Fix AddAnnotations for unstructured.Unstructured (#9164)

- 26 Other changes :seedling:

- 7 Documentation and book contributions :book: 

All merged PRs can be viewed in GitHub:
https://github.com/kubernetes-sigs/cluster-api/pulls?q=is%3Apr+closed%3A2023-08-13..2023-08-21+is%3Amerged+milestone%3Av1.6+

_Thanks to all our contributors!_ 😊
/Your friendly comms release team

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/area release

[killianmuldoon]

Could the weekly tool be a subcommand of the release-notes tool? I feel like this could become unwieldy and there's a duplication of effort. We might want another, similar, tool for emails for example.

[willie-yao]

Could the weekly tool be a subcommand of the release-notes tool? I feel like this could become unwieldy and there's a duplication of effort. We might want another, similar, tool for emails for example.

I think that's a great idea actually. There does seem like a lot of duplicated code in the weekly script. I'll work on refactoring it into the notes script.

[willie-yao]

cc @kubernetes-sigs/cluster-api-release-team

[furkatgofurov7]

Great job! One comment inline:

[furkatgofurov7]

/cc @killianmuldoon @sbueringer hey folks, could you please help reviewing this, since it is very helpful for comms team

[willie-yao]

/retest

[furkatgofurov7]

/lgtm

cc @killianmuldoon

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 8ca7f43f470b0895673a6491fa8854e643c65ff7

[furkatgofurov7]

Last nit from my side:

[furkatgofurov7]

/lgtm

cc @killianmuldoon

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 34488ea25c824bb59aaf73680116346f64d09582

[furkatgofurov7]

/test ?

[k8s-ci-robot]

@furkatgofurov7: The following commands are available to trigger required jobs:

• /test pull-cluster-api-build-main
• /test pull-cluster-api-e2e-full-dualstack-and-ipv6-main
• /test pull-cluster-api-e2e-full-main
• /test pull-cluster-api-e2e-main
• /test pull-cluster-api-e2e-mink8s-main
• /test pull-cluster-api-e2e-workload-upgrade-1-28-latest-main
• /test pull-cluster-api-test-main
• /test pull-cluster-api-test-mink8s-main
• /test pull-cluster-api-verify-main

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-apidiff-main
• /test pull-cluster-api-e2e-scale-main-experimental

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-api-apidiff-main
• pull-cluster-api-build-main
• pull-cluster-api-e2e-main
• pull-cluster-api-test-main
• pull-cluster-api-verify-main

In response to this:

/test ?

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/test-infra repository.

[furkatgofurov7]

/test pull-cluster-api-e2e-main

[killianmuldoon]

/approve

Thanks for this - good to see the quick evolution of the release tools this cycle!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: killianmuldoon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [killianmuldoon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-infra-cherrypick-robot]

@willie-yao: #9343 failed to apply on top of branch "release-1.5":

Applying: Add weekly update script
Using index info to reconstruct a base tree...
M	Makefile
M	docs/release/release-tasks.md
M	hack/tools/release/notes.go
Falling back to patching base and 3-way merge...
Auto-merging hack/tools/release/notes/main.go
CONFLICT (content): Merge conflict in hack/tools/release/notes/main.go
Auto-merging docs/release/release-tasks.md
CONFLICT (content): Merge conflict in docs/release/release-tasks.md
Auto-merging Makefile
CONFLICT (content): Merge conflict in Makefile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add weekly update script
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.5

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/test-infra repository.

[k8s-infra-cherrypick-robot]

@willie-yao: #9343 failed to apply on top of branch "release-1.4":

Applying: Add weekly update script
Using index info to reconstruct a base tree...
M	Makefile
M	docs/release/release-tasks.md
M	hack/tools/release/notes.go
Falling back to patching base and 3-way merge...
Auto-merging hack/tools/release/notes/main.go
CONFLICT (content): Merge conflict in hack/tools/release/notes/main.go
Auto-merging docs/release/release-tasks.md
CONFLICT (content): Merge conflict in docs/release/release-tasks.md
Auto-merging Makefile
CONFLICT (content): Merge conflict in Makefile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add weekly update script
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.4

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/test-infra repository.

[killianmuldoon]

Like with the release notes tool it would be better IMO to only ever use this from main instead of trying to backport all changes.