chore: modernize ruff config

[afuetterer]

Description

The ruff project deprecated sections under [tool.ruff]. You need to have e.g. [tool.ruff.lint].

See: https://docs.astral.sh/ruff/configuration/

• fix ruff issues

Types of Changes

• Build related changes

Checklist

• I have read the contributor guide.
• My code follows the code style of this project.
• All new and existing tests passed.

[MyPyDavid]

nice, thanks @afuetterer! Should we not make a ruff.toml ?? think it would be cool ;)

[jochenklar]

No please put everything in pyproject.toml if that works.

[MyPyDavid]

the more .toml the merrier 😄

[jochenklar]

The idea of the pyproject.toml is that you can put almost everything in it and not clutter your repo's root with files. sadly it does not work for everything.

[afuetterer]

Thanks for fixing the ruff issues @MyPyDavid

[MyPyDavid]

rebased on dependency-updates

[MyPyDavid]

still open

=========================== short test summary info ============================
FAILED rdmo/core/tests/test_project_status.py::test_package_json_and_pre_commit_versions_match - AssertionError: assert {'eslint': '8...ct': '18.2.0'} == {'eslint': '8...ct': '18.2.0'}
  
  Omitting 2 identical items, use -vv to show
  Differing items:
  {'eslint-plugin-react': '7.34.0'} != {'eslint-plugin-react': '7.33.2'}
  
  Full diff:
    {
        'eslint': '8.54.0',
  -     'eslint-plugin-react': '7.33.2',
  ?                                ^ ^
  +     'eslint-plugin-react': '7.34.0',
  ?                                ^ ^
        'react': '18.2.0',
    }
========== 1 failed, 23472 passed, 179 warnings in 1268.59s (0:21:08) ===================================== short test summary info ============================
FAILED rdmo/core/tests/test_project_status.py::test_package_json_and_pre_commit_versions_match - AssertionError: assert {'eslint': '8...ct': '18.2.0'} == {'eslint': '8...ct': '18.2.0'}
  
  Omitting 2 identical items, use -vv to show
  Differing items:
  {'eslint-plugin-react': '7.34.0'} != {'eslint-plugin-react': '7.33.2'}
  
  Full diff:
    {
        'eslint': '8.54.0',
  -     'eslint-plugin-react': '7.33.2',
  ?                                ^ ^
  +     'eslint-plugin-react': '7.34.0',
  ?                                ^ ^
        'react': '18.2.0',
    }
========== 1 failed, 23472 passed, 179 warnings in 1268.59s (0:21:08) ==========

Is there a way to get and post the test summary somewhere else via the github action? (for when it fails)

[afuetterer]

What do you mean?
Have the result of this test as an github action output?
Is this test significant enough for that?

[MyPyDavid]

No, I mean the failed test summary in general. Could it be posted in the actions summary for example (as a convenience)?

This rdmo/core/tests/test_project_status.py::test_package_json_and_pre_commit_versions_match is more like a build test right? Think it could be ran and failed first in the pytest order, but it is not for in this PR.
The name test_project_status is maybe a bit confusing because it overlaps with the rdmo.projects, I think build or package _status would fit better.

[afuetterer]

Sure, that is possible. Naming was done hacky as well, feel free to rename.

Can you open an issue about that?

If this PR is done, lets merge it into dependency-updates and deal with the other issue seperately.

[MyPyDavid]

yes