Release Notes linting improvements

[npolshakova]

What would you like to be added:

Add tooling to check release notes maps before they are merged into sig-release to prevent invalid yaml and catch common errors.

Why is this needed:

The release notes team's handbook has a number of listed TODOs. Adding a workflow to check invalid yaml, spelling, grammar and punctuation checks would help automate the review process

Also see: kubernetes/sig-release#2498

[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

[xmudrii]

@npolshakova I remember some PRs about this topic, is this issue still relevant?

[puerco]

I think krel release-notes validate is the implementation and the new workflow should close this: kubernetes/sig-release#2698

(these supersede kubernetes-sigs/release-actions#101 )