Adding the release drafter action to create draft release notes

[emawby]

Description

One Line Summary

Adding the release drafter action to create draft release notes.

Details

As PRs are merged to main release drafter will create a draft release and fill out the release notes template.
PRs will be bucketed into fix, feature, or improvement based on labels. We need to tag our PRs with the appropriate labels to get the automatic bucketing. However PRs can always be moved around when we create the release PR.

Motivation

More consistent release notes across SDKs and working towards more automated release processes

Scope

Release notes

Testing

Unit testing

N/A

Manual testing

I have tested this action in a private repo

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is