Uv, repository versioning, release automation

[GinaStavropoulou]

This is still a draft as I have not finished with the versions yet.

• I have pinned the versions of all packages and not the pyproject.toml files are uv-friendly
• I have added the uv.lock files which are needed for "freezing" the dependencies.
• Uv sync is also used in the dockerfiles instead of uv pip install
• I also tried to separate the installation of requirements and the installation of the package and common as suggested here - but I am not sure if this is really the optimal way.
• I also substituted the requirements-dev.txt file with a pyproject.toml - I hope the action with the mkdocs will work.
• Generally I tried to use UV everywhere apart from some pip usage like here

[balazsdukai]

Closes #75
Closes #72

[balazsdukai]

• Added a release automation workflow to maintain the version numbers, create a new release with the release notes from CHANGELOG.md and open a PR to merge back the release from master to develop
• Added CHANGELOG.md
• Unified the ruff format config into the root pyproject.toml
• Set dependency versions to compatible (~=) instead of minimum required
• Document the release process