configuration for release notes generation

[MatteoGuarnaccia5]

Description

Added configuration for custom auto generated release notes.
Made relevant changes in documentation.

The same changes would need to be made in ims-api

Testing instructions

Add a set up instructions describing how the reviewer should test the code

• Review code
• Check Actions build
• Review changes to test coverage
• {more steps here}

Agile board tracking

closes #806

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.15%. Comparing base (2fcbad3) to head (2957e12).
Report is 349 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #874      +/-   ##
===========================================
+ Coverage    96.19%   99.15%   +2.96%     
===========================================
  Files          138       72      -66     
  Lines        33685    16041   -17644     
  Branches      4914     2978    -1936     
===========================================
- Hits         32402    15905   -16497     
+ Misses        1275      132    -1143     
+ Partials         8        4       -4     

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

[MatteoGuarnaccia5]

An example of what the changelog now looks like with the new config

[joshuadkitenge]

Here is a guide for best practices for change logs Github:
https://keepachangelog.com/en/1.0.0/

[MatteoGuarnaccia5]

This PR is an example for custom changelogs, which are categorized based off the the labels on pull requests. An example file has been included to show a workflow that automatically labels pull requests based off of their branch name. This change would mean making changes to the wiki, the pull request template, and optionally the readMe.

The labels used in this PR are examples, you can pick whatever labels / rules to use for future. But should be included in any documentation created.