Add global release notes template

[dsimansk]

Changes

• 🎁 Add global release notes template

The format is a merge between our common templates we use in release blog and k8s release-notes tool we used so far.

With the template in place, release leads don't have to execute GH action to produce release notes in .md and copy it over. Rather press Generate release notes button in release edit view.
Future enhancement to consider, the process can be further automated with GH API calls, it's not 1 step process, but rather a chain. In a nutshell POST to generate notes with inputs -> content in response -> POST to edit/update release body.

/cc @knative/knative-release-leads
/cc @knative/technical-oversight-committee

Fixes knative/community#1499

Based on docs:
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#example-configurations

Preview from knative/client current main:

Preview in markdown format:

<!-- Release notes generated using configuration in .github/release.yml at main -->
## What's Changed
### 💫 New Features & Enhancements
* Add option flags to define nodeSelector, nodeAffinity and toleration on Knative Service by @Shashankft9 in https://github.com/knative/client/pull/1924
### 🛠 Other Changes
* Add release note template by @dsimansk in https://github.com/knative/client/pull/1956

## New Contributors
* @Shashankft9 made their first contribution in https://github.com/knative/client/pull/1924

**Full Changelog**: https://github.com/knative/client/compare/knative-v1.14.0...v0.0.1-release-notes

[knative-prow]

@dsimansk: GitHub didn't allow me to request PR reviews from the following users: knative/knative-release-leads, knative/technical-oversight-committee.

Note that only knative-extensions members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Changes

• 🎁 Add global release notes template

The format is a merge between our common templates we use in release blog and k8s release-notes tool we used so far.

With the template in place, release leads don't have to execute GH action to produce release notes in .md and copy it over. Rather press Generate release notes button in release edit view.
Future enhancement to consider, the process can be further automated with GH API calls, it's not 1 step process, but rather a chain. In a nutshell POST to generate notes with inputs -> content in response -> POST to edit/update release body.

/cc @knative/knative-release-leads
/cc @knative/technical-oversight-committee

Fixes knative/community#1499

Based on docs:
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#example-configurations

Preview from knative/client current main:

Preview in markdown format:

<!-- Release notes generated using configuration in .github/release.yml at main -->
## What's Changed
### 💫 New Features & Enhancements
* Add option flags to define nodeSelector, nodeAffinity and toleration on Knative Service by @Shashankft9 in https://github.com/knative/client/pull/1924
### 🛠 Other Changes
* Add release note template by @dsimansk in https://github.com/knative/client/pull/1956

## New Contributors
* @Shashankft9 made their first contribution in https://github.com/knative/client/pull/1924

**Full Changelog**: https://github.com/knative/client/compare/knative-v1.14.0...v0.0.1-release-notes

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-sigs/prow repository.

[dsimansk]

/cc @knative-extensions/technical-oversight-committee
/cc @knative-extensions/knative-release-leads

[psschwei]

+1 from me

[Leo6Leo]

+1, it looks good!

[dprotaso]

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, dsimansk

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dprotaso,dsimansk]

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