Fix/pre commit

[joyet-simon]

Reason for change

Code changes

How to test

As a reviewer, you are encouraged to test the PR locally.

Checklist for authors and reviewers

• The title of the PR uses business wording, not technical jargon, for the changelog readers to understand it
• The PR implements the changes asked in the referenced task / issue
• The automated tests are compliant with the testing strategy
• The tests are relevant, and cover the corner/error cases, not only the happy path
• You understand the impact of this PR on existing code/features
• The changes include adequate logging and Datadog traces
• Documentation is updated (API, developer documentation, ADR, Notion...)

Non applicable

[sonarqubecloud]

Quality Gate passed

Issues
2 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

[joyet-simon]

@alma/squad-devx Can you make a review please?

[remi-zuffinetti]

Do we really need to add one Dockerfile per dev tool we want to use?

I can approve now if it unlocks you, but I think it would be better to have a single kind of "devbox" like we have in main to run all our linters, if they require to be run with Docker.