feature:Add a mutation-testing setup for compliance and invoice, exte……nding #94's treasury-only coverage

[nzubepolycap-hub]

closes #470

Work Summary

Objective

Extend the existing treasury mutation-testing workflow with equivalent jobs for
the compliance and invoice contracts.

Changes Made

• Added a mutants-compliance GitHub Actions job in
  .github/workflows/test.yml.
  • Runs only for workflow_dispatch.
  • Installs Rust 1.95.0 and cargo-mutants.
  • Targets contracts/compliance/src/allowlist.rs.
• Added a mutants-invoice GitHub Actions job in
  .github/workflows/test.yml.
  • Runs only for workflow_dispatch.
  • Installs Rust 1.95.0 and cargo-mutants.
  • Targets contracts/invoice/src/invoice.rs.
• Preserved the existing mutants-treasury job structure and behavior.
• Installed Rust locally with rustup so the workspace could be validated.
• Corrected the compliance-client dependency configuration.
• Updated stale invoice test calls to match the current create_invoice API.
• Updated stale compliance and treasury test calls to match current contract
  entrypoint signatures.
• Removed or corrected stale test helper and snapshot API assumptions.
• Cleaned up related unused variables, imports, and lifetime annotations.

Branch and Commit

• Branch: COMEBACKHERE-contracts470
• Commit: ff4cbff
• Commit message: feature:Add a mutation-testing setup for compliance and invoice, extending #94's treasury-only coverage

Validation

The following required command sequence was run:

cargo test --all
cargo clippy --all -- -D warnings
cargo fmt --all -- --check

Validation did not complete successfully. The test phase still reports
remaining legacy test-suite issues, including duplicate invoice test
definitions, outdated create_invoice calls missing the merchant_nonce
argument, and calls to APIs whose current return types no longer provide
.unwrap().

The workflow configuration itself is present and both new mutation jobs are
gated behind manual workflow_dispatch runs.

[drips-wave]

@nzubepolycap-hub 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