Updating documentation: Post 1.30 Release Notes Updates

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

[x] 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
[x] 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 https://github.com/kubernetes/kubernetes/issues/124046
[x] Need to update the roles and responsibilities of the Release Notes team, and distinguish responsibilities between Release Notes and Comms
- This was updated in https://github.com/kubernetes/sig-release/commit/8cf9a5b446e34b7bc8571dc28b533504e3a7761c
[ ] (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.
[x] Add a common debug section
- https://kubernetes.slack.com/archives/CN1KH4K9A/p1712045966265629
- https://kubernetes.slack.com/archives/C06DZERRB38/p1710423295724509

kubernetes / sig-release