CHORE: Setting up ruff

[ecoussoux-ansys]

Description

This PR introduces the use of ruff for linting and formatting, replacing isort, black and flake8.
ruff is an extremely fast Python linter and code formatter, that integrates the functionalities of several tools behind a single, common interface (https://docs.astral.sh/ruff/)
Its implementation in pyaedt was suggested in issue #4775.
This PR can also be seen as contributing to the efforts described in issue #5504.

It should be noted that ruff does not replace the following tools, whose use in the project is therefore not affected by the changes made in this PR:

• blacken-docs (used for formatting Python code blocks in documentation files): ruff does not support formatting/linting of embedded code (particularly in .rst or .md files, see ☂️ Formatter: Support formatting of embedded code astral-sh/ruff#8237). Similarly, blacken-docs does not support the ruff formatter as an alternative for black (see Support Ruff formatter as an alternative for Black adamchainz/blacken-docs#352). This tool is therefore retained (as a pre-commit hook), despite the remaining dependence on black,
• codespell (fixes common misspellings in source code and other files): Is not integrated into ruff (see Request: Spelling check astral-sh/ruff#1628),
• numpydoc (used for formatting docstrings): Is also not integrated into ruff (see Feature request: numpydoc rules astral-sh/ruff#8425).

The changes in this PR are limited to the definition of a minimal configuration for ruff (in the pyproject.toml file) with only a few rules applied to the code base, together with the introduction of pre-commit hooks for linting and formatting with ruff. Python files fixed by ruff are updated. Configurations for isort, black and flake8 are removed and the associated pre-commit hooks are also dropped.
The currently ignored rules shall be gradually applied to the project in subsequent PRs. For this task, a useful command-line instruction can be used, which will return the number of errors flagged for each selected rule as well as the availability of automatic fixes : ruff check . --statistics

It is also worth mentioning that the list of rules selected until now for linting in the .flake8 file is not regarded as a reference for defining the ruff configuration implemented. Instead, this config is based on the recommendations from the pyansys-dev-guide, as introduced in ansys/pyansys-dev-guide#592.
Furthermore, the enforcement of ‘PTH’ type rules is not a priority as part of the introduction of ruff to the project, as an effort in this direction is currently underway as described in issue #5180.

Issue linked

Related to #4775 and #5504.

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[codecov]

Codecov Report

Attention: Patch coverage is 90.27778% with 7 lines in your changes missing coverage. Please review.

Project coverage is 85.25%. Comparing base (459f92f) to head (77a85d2).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6157      +/-   ##
==========================================
+ Coverage   84.41%   85.25%   +0.84%     
==========================================
  Files         170      170              
  Lines       64119    64119              
==========================================
+ Hits        54125    54666     +541     
+ Misses       9994     9453     -541     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[SMoraisAnsys]

Thanks for the contribution @ecoussoux-ansys ! I left some minor changes that need to be taken care of before merging