infra: add release tracking issue template

[vitorfloriano]

Description

This PR adds am issue template for planning releases.

I took inspiration from:

• https://github.com/kubernetes-sigs/node-feature-discovery-operator/blob/44051dd902f5dcb4a4f021c45a53c2eeb0d1ea61/.github/ISSUE_TEMPLATE/release.md?plain=1
• https://github.com/kubernetes-sigs/cluster-api/blob/94a0ca7ef3760745007b06bf63820a8358b8dec2/.github/ISSUE_TEMPLATE/release_tracking.md?plain=1#L4

You can check the rendered issue in vitorfloriano#18.

Open Questions

1. Should the release planner issue be separate from the release proposal issue? Putting it all together looks a bit bloated.
2. Should the checklist be a bit more compact with only the checkboxes for each step (without much details)? The release sheperd could follow the instructions in release.md and only use the release tracking issue as a checklist. We could also link each step to a section in release.md for guidance (see https://github.com/kubernetes-sigs/cluster-api/issues/new?template=release_tracking.md)

I basically copy/pasted the instructions and added checkboxes. That may not be the best way to go about it.

Related Issue

xref #151

Type of Change

/kind cleanup

Testing

I opened an issue on my fork to test this changes: vitorfloriano#18

(blooper: I didn't foresee that Github would resolve the # in the commit list and now a bunch of PRs have a callback to my test issue. my apologies 😓 )

[netlify]

✅ Deploy Preview for node-readiness-controller ready!

Name	Link
🔨 Latest commit	4820503
🔍 Latest deploy log	https://app.netlify.com/projects/node-readiness-controller/deploys/6a85cd4d5f43e600080ce885
😎 Deploy Preview	https://deploy-preview-432--node-readiness-controller.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

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

[vitorfloriano]

/cc @ajaysundark @Priyankasaggu11929

[Priyankasaggu11929]

is there any example PR link we can point to here? (asking because even i don't recall what PR we need to create for this step 😅 )

[vitorfloriano]

This is the one I opened for v0.5.0 against main #412

Ajay opened for v0.4.0 against main #301 and against the release branch for the patch #306

[Priyankasaggu11929]

do these needs to be a separate PR? or same as one in above step - https://github.com/kubernetes-sigs/node-readiness-controller/pull/432/changes#r3819506009?

if same, then let's make these sub-list items?

[vitorfloriano]

Yeah, Ajay updated them in the same PR, but I didn't 😅 Need to work on that today with Ajay in our 1:1