ci: github release notes configuration

[skl]

This PR introduces a configuration file that splits the auto-generated GitHub release notes into several sections with headers. This is not release automation, it covers formatting of the release notes only, but it does apply to both manual and automated releases so can be used right away.

I took a quick look at our main commits, and found only the following (3) labels in use:

• bug
• dependencies
• documentation

So, working with what we have right now, I came up with this format:

• General
• Fixed
• Documentation
• Dependencies

I thought it might also be sensible to exclude otelbot[bot] commits, as they seem to only be "Automatic update of offsets.json", which are not useful.

This is an example and a starting point, happy for this to evolve as we go. Probably one thing we could do is be more vigilant in at least using the bug label on PRs, where appropriate to begin with?

Relates to:

• Add a project changelog #865

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.26%. Comparing base (8b80320) to head (f4eb05b).

❗ There is a different number of reports uploaded between BASE (8b80320) and HEAD (f4eb05b). Click for more details.

HEAD has 37 uploads less than BASE

Flag	BASE (8b80320)	HEAD (f4eb05b)
oats-test	5	0
k8s-integration-test	15	0
integration-test-arm	1	0
integration-test	10	0
integration-test-vm-${ARCH}-${KERNEL_VERSION}	6	0

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #868      +/-   ##
==========================================
- Coverage   55.16%   46.26%   -8.90%     
==========================================
  Files         251      251              
  Lines       21481    21481              
==========================================
- Hits        11849     9938    -1911     
- Misses       8817    10901    +2084     
+ Partials      815      642     -173     

Flag	Coverage Δ
integration-test	?
integration-test-arm	?
integration-test-vm-${ARCH}-${KERNEL_VERSION}	?
k8s-integration-test	?
oats-test	?
unittests	46.26% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.