Automated release notes

[OrlinVasilev]

*Is your feature request related to a problem? Please describe.
The current release notes are not complete and we can do better

Describe the solution you'd like
Introduce proper labels and rules for writing new PRs so we can generate Release notes automagicaly
Add release.yml to ease out a bit the process

labels to be used in the future:
For release notes:
release-note/enhancement - make something better
release-note/new-feature - completely new feature
release-note/update - update current component - e.g. Bump Golang version
release-note/breaking-change - breaking changes
release-note/docs - docs update
release-note/community - change related to community
release-note/deprecation - deprecation change

To be skipped:
release-note/ignore-for-release- no need to be added into release notes

Describe the main design/architecture of your solution
Once we have proper setup for the PRs with Labels and good description it will be just click of a button to create release notes!
Add GitHub Action on PR creation to check if you have at least one label selected - mheap/github-action-required-labels@v1

Describe the development plan you've considered
Once we have that implemented we can invoke it from actions or manual on new tag/release created!

New release notes can look like:

Here is the example repo:
https://github.com/OrlinVasilev/release/releases/tag/v0.1

---

What's Changed

Exciting New Features 🎉

• add new feature feature by @OrlinVasilev in add new feature feature OrlinVasilev/release#1

Component updates ⬆️

• update workflow by @OrlinVasilev in update workflow OrlinVasilev/release#5

Breaking Changes 🛠

• Breaking Change for demo Holder for logo #6 by @OrlinVasilev in Breaking Change for demo #6 OrlinVasilev/release#7

Deprecations ❌

• deprecation switch to vendor, and update the deploy process #2 by @OrlinVasilev in deprecation #2 OrlinVasilev/release#4

Other Changes

• add action for label check by @OrlinVasilev in add action for label check OrlinVasilev/release#3

New Contributors

• @OrlinVasilev made their first contribution in add new feature feature OrlinVasilev/release#1

Full Changelog: https://github.com/OrlinVasilev/release/commits/v0.1

[a-mccarthy]

@OrlinVasilev we should also update the docs with this new process and what the labels mean. Maybe in the contributing guide? https://github.com/goharbor/harbor/blob/main/CONTRIBUTING.md#push-and-create-pr

[a-mccarthy]

Also we should update any release docs we have. I'm not sure if there are any more specific release process docs for creating a release, though, other than this section in the releases.md file, https://github.com/goharbor/harbor/blob/main/RELEASES.md#publishing-a-new-release.

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[OrlinVasilev]

done