Fix gitleaks pre-commit configuration

[Ludy87]

Motivation

• The gitleaks pre-commit hook was configured with custom args (including the unsupported --no-git flag and a .gitleaks.toml reference) which could cause the hook to fail before scanning; switching to the upstream defaults prevents that failure.

Description

• Removed the custom args block from the gitleaks entry in .pre-commit-config.yaml so the hook uses the upstream v8.30.0 defaults.

Testing

• Ran git diff --check and a Python assertion that inspects .pre-commit-config.yaml to confirm the gitleaks hook block contains only - id: gitleaks and does not include --no-git or a --config reference (these checks passed); attempting to install/run pre-commit in this environment failed due to network/PyPI access restrictions, so an actual pre-commit run gitleaks was not executed.

---

Codex Task

[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