Look into Pylint alternatives

[Nour-Mws]

From #39 (comment), which was part of a discussion on Pylint not supporting per-directory configuration:

[tool.pylint.tests]
disable = "missing-function-docstring,invalid-name,redefined-outer-name"

The .tests on the first line is disregarded (silently), and the disable directive is applied for all modules, not just our test code.

In fact, it seems that per-directory settings for Pylint is not supported upstream (and this issues was first reported in 2015)!..
[..]
[Consider] abandon[ing]/replac[ing] Pylint altogether. We're probably not there yet, but - frankly - it's popped into the back of my mind a couple of times now:
We're running into a fair amount of issues getting it properly configured.
Some of the warnings it produces are very opinionated/strict, even when I feel the code in question looks pretty good. Refactoring our code just to make Pylint happy, is something I'd rather not have to do a lot of...
Pylint seems to have fallen out of favor in recent times compared to other linters. For example, a lot of cookiecutter repos I've looked recently does not include it among their preferred linters. Also, this blog post compares a bunch of linters, and Pylint does not come out on top.

[mknorps]

#21 is also a pylint issue

[mknorps]

We moved to ruff. This was implemented by @jherland in a series of PRs: #424, #425, #426.