ci: Add a workflow to create a GitHub Release

[dhirschfeld]

All Submissions:

• I installed pre-commit prior to committing my changes (see development setup docs).
• My commit messages conform to conventional commits.
• My PR title conforms to conventional commits.
• I linked to any relevant issues.

Changes to / New Features:

• I included docs for (the changes to) my feature.
• I wrote tests for (the changes to) my feature.

Description of changes

This implements the simplest possible automated release notes for solara. I'm adding this because an up-to-date changelog is something I've wanted and I think solara is pretty great and want it to succeed!

Resolves #206

Related:

• Add release notes #206
• Change log recommendations / improvements #1047
• Update changelog on docs #1082

[dhirschfeld]

Will automatically generate basic release notes based on the PRs merged since the previous release.

xref: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes

[dhirschfeld]

bump!

[iisakkirotko]

Thanks for opening the PR, and sorry it took a while to get reviewed. A couple small notes:

[iisakkirotko]

I do also see that @maartenbreddels has been doing release notes as a part of the docs again, not sure if he's automated the process (and if these notes should go onto the website as well)?

[dhirschfeld]

I do also see that @maartenbreddels has been doing release notes as a part of the docs again, not sure if he's automated the process (and if these notes should go onto the website as well)?

I think it's useful to have at least a listing of merged PRs between releases in the GitHub Releases page. This can be in addition to official release notes. If it's automated, and adds value - why not?!

I also like having a GitHub Release as it makes it a bit easier to view the diff betwen all releases (there's a dropdown as opposed to manually comnstructing the compare url yourself)