Release CI Workflow Enhancements

[ptheywood]

There are several things we could do to enhance future releases via the CI workflow.

• Partially automated description (Boilerplate, changelog? etc)
• Named artifacts.
  • Via gh, when attaching files to a new release rather than just passing a glob you can pass a per file string which is a pretty name for the file. I.e. `'pyflamegpu-2.0.0-py38-linux-x86.whl#PyFLAMEGPU 2.0.0-alpha for Linux X86_64' or somethign to that effect.
• Offline Docs artifact(s)
  • Currently the doxygen docs would be simplest, although it would be nice to bring breathe/sphinx into the main repo.
  • Python docs would be good too, if we were building them (Py doxygen #539)

[ptheywood]

GitHub Releases is in the process of upgrading to a new versions which includes some automation of release notes, which handle some of this for us. Unsure exactly how much until we can try it and see.

https://github.blog/2021-10-04-beta-github-releases-improving-release-experience/

[Robadob]

From the video on the page, looks like what's new is just a list of commit messages and it also did a shout out for new contributors.