Modernize Azure style checks

[A-CGray]

Purpose

Addresses #70

• Update to latest versions of black and flake8
• Update to running all style checks on ubuntu 24 & python 3.11
• Also run flake8 on python 3.13

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 flake8 and black 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

[marcomangano]

The changes look good to me. This will trigger a series of failures until we update all the downstream repos, correct?

[eirikurj]

Yeah, this will trigger failure on pretty much all our repos

[A-CGray]

Yeah it will. I wonder if we should wait a couple of weeks and make fixing these formatting issues and the associated PRs an MDOLab workshop task. Might be a good introduction to our GitHub process for the new students?

[A-CGray]

Closing as we switched to ruff for formatting and linting in #74