Updating documentation: Post 1.30 Release Notes Updates

[npolshakova]

Umbrella issue to improve the Release Notes Role Handbook to clarify some things that have been points of confusion in this (and previous) releases.

These action items are from the 1.30 end of release retro: https://docs.google.com/document/d/1RjuFr4xFuGeHUWgCDMlBgGe6SawvDhttXKj96_J5TKg/edit?usp=sharing

• The TODOs section is out of date.
  - Add example github workflow to catch invalid yaml, lining issues, spelling and past tense grammar.
  - Add write up for VSCode plugin to catch yaml edits
  - Work with sig-docs to create a dictionary of common Kubernetes terms: https://kubernetes.slack.com/archives/C1J0BPD2M/p1709129515642109
• Highlight in the handbook that improvements and fixes for krel are encouraged. Give examples in the TODOs section on potential improvements to krel and open issue
  - update krel tool to show progress of how many PRs to review are left and other bugs
  - Other known issues 1.30 Release Notes: "Known Issues" kubernetes#124046
• Need to update the roles and responsibilities of the Release Notes team, and distinguish responsibilities between Release Notes and Comms
  - This was updated in 8cf9a5b
• (Nina) Define a release notes draft PR merge deadline. Currently the timeline only defines when a branch is created, and we assume to get the PR done sometime before the next branch is made. This would be only internally enforced and used to give status updates.
• Add a common debug section
  - https://kubernetes.slack.com/archives/CN1KH4K9A/p1712045966265629
  - https://kubernetes.slack.com/archives/C06DZERRB38/p1710423295724509

[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