Changelog for 2.0.0-rc1

[Robadob]

todo

• [x] Add any changes for commits ahead of this PR
• [x] Update release date in changelog.md/citation.cff
• [x] Update visualisation repo to a new release tag.

~Waiting for these PRs before release: #1150, #1155.~ Defferred to the next release as these are blocked.

[ptheywood]

This should be rc1 not rc2. Python's rc implicitly means rc0 (see previous release' assets)

[ptheywood]

Edited the original commit to include merged but not yet included PR's / issues that will need including.

We could potentially do a pre-release with the current changes IMO, as we are blocked on the 2 outstanding ones we want before the "full" release.

I.e.

• 2.0.0-rc1 with current changes - adds a cuda 12.x pre-release
• 2.0.0-rc2 which removes < CUDA 11.2, and fixes jitify compialation time. Maybe #1156 as well.
• 2.0.0 - assuming no problems with rc1/rc2 changes after a period of time / see how conda goes.

[ptheywood]

Manually invoked the thorough CI againt this branch as of 1c5d2e3 to check for any issues which might prevent the rc1 release from working.

https://github.com/FLAMEGPU/FLAMEGPU2/actions/runs/7502099207

If this is succcessful, then rc1 can proceeed:

• [x] create matching flamegpu2-visualiser release (flamegpu-2.0.0-rc.1)
• [x] update flamegpu2-visualiser version to fetch (flamegpu-2.0.0-rc.1)
• [x] Update dates of the planned release
• [ ] Merge this PR, push the release tag (v2.0.0-rc.1)
• [ ] Write the release notes while CI runs (~1-2 hours).
  • Include breaking changes, additions, link to the changelog, pyflamegpu installation instructions.
• [ ] Publish the release with release notes.
• [ ] Create the version bump PR, which needs to be the first thing merged post release tag.

[ptheywood]

double checked that tests still path, py and c++ on linux (CUDA 12.0)