Pre-commit still runs `cargo contract build` despite ISSUES_RESOLUTION.md switching the hook to `cargo check`

[nanaf6203-bit]

Context: ISSUES_RESOLUTION.md records resolving the slow cargo contract build pre-commit hook by replacing it with cargo check, but .pre-commit-config.yaml still contains both a cargo-check hook AND a cargo-contract-build hook (under Contract-specific checks).

Problem: The resolved issue is contradicted by the config: every contracts change still triggers the slow wasm build locally, and the two hooks duplicate checking with different tools, making pre-commit runs slow and confusing.

Proposed approach: Keep cargo check (fast, correct for ink! prototyping), delete the cargo-contract-build hook, and re-record the resolution; verify unchanged behavior via pre-commit run --all-files.

Acceptance criteria: pre-commit config has one build-check hook; runtimes clearly faster; ISSUES_RESOLUTION reflects the final state.

[mercy60]

@mercy60 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello maintainer. Can I work on this please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mercy60 to this issue.

[drips-wave]

Congratulations, @mercy60! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @mercy60: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊