Use `TagBot` config to auto-generate GitHub release descriptions

[lgoettgens]

Is your feature request related to a problem? Please describe.
When we want to release a new version of Oscar, one of @benlorenz and @aaruni96 pings the registrator with @JuliaRegistrator register followed by the part of our changelog that refers to the to be made release.
Once the registration went through, TagBot then creates a GitHub release on that commit and pre-fills the commit description with a list of all merged PRs and closed issues. Everyone that subscribes to the notifications of our repository then gets an email stating that a new version has been released, and the description.
A few minutes later, someone then usually edits the GitHub release description to instead contain the part of our changelog.

This is an unnecessary manual step of work, and it would be great to already have the proper changelog in the notification email (instead of the more or less useless github auto-generated stuff).

Describe the solution you'd like
One can pass some config flags to TagBot to control how the GitHub release description looks like. This includes options to include the string that was passed to the registrator. See https://github.com/JuliaRegistries/TagBot?tab=readme-ov-file#changelogs for more details on this.

Additional context
The same change should be applied to all of our other repositories, once they start doing proper changelogs.

[JuliaRegistrator]

Error while trying to register: "Pre-release version not allowed"