Add bump-my-version for managing updating release versions

[StephanieKemna]

Description

Resolves #90

We had no system for how to update the release nr in multiple files, apart from that I recently documented that in the README.
bump-my-version should allow for doing this automatically when we create a release.

Updated dependencies in pyproject.toml to include bump-my-version (do a uv sync -U to get it).

How Has This Been Tested?

• uv run bump-my-version bump patch --dry-run -vv --allow-dirty

Developer Checklist (before requesting PR review)

• My code follows the style guidelines of this project
• My changes generate no new warnings
• [n/a] Any dependent changes have been merged and published in downstream modules

I have:

• [n/a] commented my code, particularly in hard-to-understand areas
• performed a self-review of my own code
• not committed unnecessary formatting changes, thereby occluding the actual changes (e.g. change of tab spacing, eol, etc.)
• made corresponding changes to the documentation
• added change to CHANGELOG.md
• [n/a] added tests that prove my fix is effective or that my feature works (for core features)

Reviewer checklist

I have:

• performed a review of the code
• tested that the software still works as expected
• checked updates to documentation
• checked that the CHANGELOG is updated

[StephanieKemna]

@ClaasRostock @davidhjp01 @Jorgelmh ; I made this a draft since I am not 100% sure. I have not dared to run it (apart from a local dry run). I just followed the docs. It has the default config, which I adapted to say which files to change (and how). Then it has the default GitHub action, which I have not tried to run - because I would assume it would update the version before we want that to happen..

I am assuming we want to add this to publish_release or some other workflow - which one would be best?