Use Semantic Versioning to generate CHANGELOG.md

[macinsight]

Instead of manually updating the changelog.md, it could be a good idea to use the GItHub Releases' "Generate Release Notes" feature. This automatically adds Release notes, including merged PRs, contributors et cetera.

[macinsight]

We could also forego the Releases feature (As that might just not fit the usecase, remains to be seen), and instead implement another workflow, e.g the Release Changelog Builder, which also supports differing branches.

[macinsight]

Or, if we implement semantic versioning from #74 (as it’s currently configured in that PR), we could use this action to generate the changelog.md

[macinsight]

Update: I'm testing the workflow on the branch "ci" to see if it even works the way I want it to. So far, so... meh.

[macinsight]

Yay, it works!
@coavins If you want, you can merge. I keep forgetting which models I added, the auto-generated CL helps tremendously with that.

[macinsight]

Update: Fails to work after working the first time, see #93

@coavins You might have to create a repository secret, e.g CHANGELOG_BUILD_TOKEN with specific permission for the token give the github.token, AKA GITHUB_TOKEN, which is autogenerated each time a workflow kicks off, the permissions contents: write so that it can commit and pull-request: write so that the changelog can be committed and doesn’t fail while telling me it didn’t.

[macinsight]

Workflow is failing, will be revisited and tested in another repository so I can rule out issues