🌱 [WIP] hack: add weekly update script for Slack

[oscr]

What this PR does / why we need it:

This script 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/weekly.go --from 2023-02-20 --to 2023-02-26

Weekly update :rotating_light:
Changes from 2023-02-20 to 2023-02-26 a total of 35 new commits where merged into main.

- 1 Proposals :memo: 
	 - update autoscaling from zero proposal (#8036)

- 3 Breaking Changes :warning: 
	 - Add filter to associate variables with specific patches (#8128)
	 - in-place propagation from MD to MS (#8110)
	 - in-place propagation from MS to Machines (#8111)

- 2 Feature additions :sparkles:
	 - docs: fix command-line-tools links in book (#8162)
	 - Add support for KCP remediation during cluster provisioning (#7963)

- 5 Bug Fixes :bug: 
	 - MD controller: fix nil pointer when OnDelete policy is used (#8184)
	 - Fix flaky TestServerSideApplyWithDefaulting test (#8166)
	 - Requeue health check during the creation of a new cluster accessor (#8122)
	 - ClusterClass: run dry-run on original and modified object (#8139)
	 - KCP: fix rollout after upgrade (#8125)

- 16 Other changes :seedling:

- 8 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-02-20..2023-02-27+is%3Amerged+milestone%3Av1.4+

_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 #

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

@oscr: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-e2e-informing-main	5fc601b	link	false	/test pull-cluster-api-e2e-informing-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle rotten

[willie-yao]

/remove-lifecycle rotten

[sbueringer]

What is the state of this PR? Does someone want to take it over?

[oscr]

@sbueringer I am semi back from sick leave so honestly I'm not up to speed with current comms team. But given it's marked as rotten by them I'm going to close it.

[sbueringer]

Welcome back!

I think actually @willie-yao removed rotten and the bot just added it over time before

[willie-yao]

Welcome back @oscr! I think the current comms team wanted to revive this PR and get it merged for generating weekly announcements. We can open a new PR if you'd prefer, or we can reopen the current PR.

[sbueringer]

I think if you want to take it over you have to open a new PR as you don't have the permissions to push on this PR

[willie-yao]

Opened #9343 to continue work on this!