Make ruff more verbose

[hmpf]

In ruff --output-format=full is the default.
And the statistics flag shortens the output too much to be helpful when developing

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.18%. Comparing base (622cfad) to head (80e6a74).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1084   +/-   ##
=======================================
  Coverage   81.18%   81.18%           
=======================================
  Files         140      140           
  Lines        5076     5076           
=======================================
  Hits         4121     4121           
  Misses        955      955           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[elfjes]

question though, if the statistics flag doesn't exist anymore, why did it still shorten the output?

[hmpf]

I have no idea. Removing it fixed the problem, and I couldn't find it described in the ruff docs. (If I run my locally installed ruff check -h, however...) We used a "how to convert from flake8 to ruff"-guide that might very well have been outdated.

It's not mentioned anywhere that (some?) --output-format is incompatible with --statistics. With flake8 you could use both at the same time and have both a useful view of the problem and a count.

[johannaengland]

I don't get from this PR what it actually fixes. Was any pre-commit run failing? What was the output?

https://docs.astral.sh/ruff/configuration/#full-command-line-interface - statistics is still in use and when I locally run ruff check --statistics it outputs nothing when there are no linting problems and this for example when there are:

1	F841	[*] unused-variable
[*] fixable with `ruff check --fix`

[elfjes]

Yeah, so that output is not helpful for a developer. They (or at least: I) want to see which files and which lines are not passing so that they can have a look manually. With the statistics flag that's very hard to figure out

[johannaengland]

That makes sense, then I will just amend the body of this PR to clarify this