feat: add comprehensive code metrics tracking

[bytebinders]

🚀 Pull Request

📋 Description

This PR implements a comprehensive code metrics tracking system for the TeachLink smart contract repository. It provides systematic monitoring for code complexity, duplication, and test coverage, and generates a unified quality report to ensure long-term maintainability.

🔗 Related Issue(s)

• Closes Add comprehensive code metrics tracking #376

🎯 Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 📚 Documentation update
• 🔧 Tooling/Infrastructure
• 🧪 Test improvements
• 🔒 Security fix
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvements

📝 Changes Made

• Duplication Monitoring: Configured jscpd (.jscpd.json) and added scripts/metrics-duplication.sh to track code clones.
• Complexity Analysis: Created testing/quality/complexity_analyzer.rs and updated metrics_collector.rs to measure cognitive and cyclomatic complexity.
• Unified Reporting: Implemented scripts/generate_metrics_report.sh which aggregates all metrics into a consolidated Markdown report.
• DevEx Integration: Updated install-deps.sh and validate-env.sh to include mandatory checks for coverage and metrics tools.
• Workspace Configuration: Added rust-code-analysis and chrono dependencies to the workspace and testing packages.

🧪 Testing

✅ Pre-Merge Checklist (Required)

• 🧪 Unit Tests: I have run cargo test --lib and all tests pass
• 🔨 Debug Build: I have run cargo build and the project builds successfully
• 🎯 WASM Build: I have run cargo build --target wasm32-unknown-unknown --release and WASM builds successfully
• 📝 Code Formatting: I have run cargo fmt --all -- --check and code is properly formatted
• 🔍 Clippy Lints: I have run cargo clippy and there are no new warnings

🧪 Additional Testing (Recommended)

• 📚 Documentation: I have run cargo doc --no-deps and documentation builds without errors
• 🔒 Security Audit: I have run cargo audit and no critical vulnerabilities found
• 🖱️ Manual Testing: I have verified the report generation script scripts/generate_metrics_report.sh correctly identifies existing coverage and duplication data.

📋 Test Results

./scripts/validate-env.sh
# Verified that cargo-llvm-cov, cargo-tarpaulin, and jscpd are correctly detected.

./scripts/generate_metrics_report.sh
# Verified the creation of reports/metrics_summary.md with integrated data.

🔍 Review Checklist

📝 Code Quality

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors

🧪 Testing Requirements

• I have added/updated tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Integration tests have been updated (if applicable)

📚 Documentation

• I have updated the documentation accordingly (TESTING_PLATFORM.md)
• I have updated the CHANGELOG (if applicable)

🔒 Security

• I have not committed any secrets, keys, or sensitive data
• I have considered security implications of my changes
• My changes do not introduce known vulnerabilities

🏗️ Contract-Specific (if applicable)

• Storage changes are backward compatible (N/A - Tooling only)
• Event emissions are appropriate and documented
• Error handling is comprehensive
• Gas/resource usage has been considered

📸 Screenshots/Recordings

N/A - CLI and Markdown reports.

💥 Breaking Changes

• No breaking changes introduced.

📊 Performance Impact

• CPU/Memory: Minimal; metrics tools are run only during development/CI.
• Gas costs: N/A
• Network: N/A

🔒 Security Considerations

• Risks: None; these are development-time tools.
• Mitigations: Tools are run in isolated environments or locally.

📖 Additional Context

This implementation provides a solid foundation for tracking "Technical Debt" and "Maintainability Index" as the contracts grow in complexity.

🚀 Deployment Notes

• No deployment changes needed (Tooling only)

---

🎯 Ready for Review:

• Yes, all required checks pass and I'm ready for review

[drips-wave]

@bytebinders 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