chore: suppress noisy Biome rules in Codacy

[JohnnyVicious]

Summary

• Adds biome.json disabling noNodejsModules and useTopLevelRegex
• These two rules account for ~63% of Codacy findings (63 of 100 on page 1) but are false positives: this is a Node.js project and test regexes don't need top-level hoisting
• Remaining 614 → ~230 actionable issues after suppression

Action required

After merge, enable "Use configuration file" for the Biome tool in Codacy's Code Patterns settings.

Test plan

• Verify Codacy re-analyzes after merge and noisy rules no longer appear

[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

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

This PR successfully introduces a biome.json configuration file to suppress the noNodejsModules and useTopLevelRegex rules, addressing identified false positives in the linting process. The implementation matches all defined acceptance criteria. Codacy results remain up to standards, and no merge-blocking issues or performance regressions were found.

Test suggestions

• Verify that the biome.json file adheres to the official Biome schema and syntax.
• Ensure the configuration correctly disables the specified rules when running biome lint locally.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Ensure the configuration correctly disables the specified rules when running `biome lint` locally.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}