Use same ruff command on CI and in pre-commit

[vjousse]

🔧 Problem

Currently we have different linting rules for ruff in the CI and in the pre-commit hook (we use --extended-select I in the CI/package.json and we don't in the pre-commit, error on my side).

We use a dedicated pre-commit hook to fix/lint the python code when committing, but on the CI we use our usual npm lint:all script to check that everything is ok.

If we modify our linting in package.json, it will not be reflected on the pre-commit hook and vice-versa.

🍰 Solution

Use npm fix commands in the pre-commit hook to be consistent with the CI.

🚨 Points to watch / comments

I've added the --force-exclude to the ruff params so that it excludes files that are mentioned in pyproject.toml (it's not the default behavior when a filename is specified as a parameter and that's what pre-commit does)

The format and check commands for ruff are a little bit weird. format require a --check flag to not write changes to files, and check requires the opposite (--fix) to write changes to files. At some point they will be unified (see astral-sh/ruff#8232) but it's not the case yet.

🏝️ How to test

npm lint:all and npm fix:all should work as usual.