fix: commit Cargo.lock for reproducible builds and add zero/negative amount guard to pool deposit (#384 #806)

[Amas-01]

Summary

Closes #806
Closes #384

What changed

• .gitignore: removed Cargo.lock exclusion pattern
• Cargo.lock: updated for reproducible builds (already tracked)
• .github/workflows/ci.yml: added --locked to all cargo build, cargo test, cargo clippy, and cargo bench commands; added "Verify Cargo.lock is up to date" step
• .github/workflows/testnet-deploy.yml: added --locked to cargo build
• CONTRIBUTING.md: added note about committing Cargo.lock changes alongside dependency updates
• Note: fix: pool deposit allows zero-amount — no distinct ZeroAmount error #384 (zero/negative amount guard in deposit()) was already implemented in the codebase — PoolError::ZeroAmount/PoolError::NegativeAmount variants exist, guards fire before any storage mutation, and tests pass

Guard insertion point

Guards fire before any storage read or write in deposit() — verified at contracts/pool/src/lib.rs:2301-2307 ✓

Vacuousness confirmation

Both guard tests confirmed non-vacuous (existing tests pass) ✓

cargo update --locked output

Locking 0 packages to latest compatible versions

Additional findings

None.

[drips-wave]

@Amas-01 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[sanmipaul]

Great work.