Switch to Ruff linting and formatting

[kanekosh]

Purpose

Expected time until merged

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

Checklist

• I have run ruff check and ruff format to make sure the Python code adheres to PEP-8 and is consistently formatted
• I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• I have run unit and regression tests which pass locally with my changes
• I have added new tests that prove my fix is effective or that my feature works
• I have added necessary documentation

[A-CGray]

Any idea what's going on with the failing tests @kanekosh ? Seems to be related to the version of OpenMDAO as it doesn't occur on the stable images

[kanekosh]

Any idea what's going on with the failing tests @kanekosh ? Seems to be related to the version of OpenMDAO as it doesn't occur on the stable images

@sabakhshi one of the multi-section tests (test_multi_single.py) is failing with OM 3.40 but I don't know why. Could you give it a look?

This failing test is separate from the ruff fixes here (I reproduced the test failure on the main branch too), so we should fix the test in a separate PR and meanwhile we can override and merge this PR.