Modernize linting setup and add pre-commit checks in CI

[nesnoj]

Summary of the discussion

This PR modernizes the linting and code quality setup for the project using ruff. It also establishes automated pre-commit checks in CI (new workflow: .github/workflows/pre-commit.yml) to ensure consistent code quality across all contributions.

• You can check it by reinstall open-mastr (pip install -e .[dev]) and committing something or run pre-commit run --all-files
• On commit, the pre-commit hooks should be automatically installed
• Currently the directories postprocessing/ and open_mastr/soap_api/ are excluded from the tests as they will be removed soon so there's no need to bother about the code quality right now.
• Important: The linting has NOT been applied to the repo yet! This should be done first as the new CI workflow will fail until all code has been fixed.
• Includes changes from Limit number of parallel CI jobs #669 so that one should be merged first

Workflow checklist

Automation

Closes #584

PR-Assignee

• 🐙 Follow the workflow in CONTRIBUTING.md
• 📝 Update the CHANGELOG.md
• 📙 Update the documentation

Reviewer

• 🐙 Follow the Reviewer Guidelines
• 🐙 Provided feedback and show sufficient appreciation for the work done

[FlorianK13]

I remember that @nesnoj expects a larger diff when linting the whole repo. We used black until now - will there be such a large difference in the codebase between ruff and black linting?

[nesnoj]

I remember that @nesnoj expects a larger diff when linting the whole repo. We used black until now - will there be such a large difference in the codebase between ruff and black linting?

Yes, definitely! Black only covers some aspects of code quality. Furthermore, in this case ruff is configured quite extensively.
I showcased the changes in #694 .
The most important question is: when do we want to lint the codebase? I propose to do it as last step before the next release.