ci: enforce WASM size checks for all publishable contracts

[iammrjude]

Summary

Closes #138

This PR extends the WASM size check so CI covers every publishable Soroban contract crate in the workspace instead of relying on a hard-coded package list.

What changed

• updated scripts/check-wasm-size.sh to:
  • discover contract manifests under contracts/*/Cargo.toml
  • include every crate that exposes a cdylib target
  • build all discovered contracts with the existing workspace release profile
  • print exact WASM byte sizes and remaining headroom in CI logs
  • fail if any expected artifact is missing
  • fail if any artifact exceeds Soroban's 64 KiB limit
• updated .github/workflows/ci.yml to run the size-check script with bash
• added README contributor notes for:
  • cargo fmt --all
  • cargo clippy --all-targets --all-features -- -D warnings
  • cargo test
  • ./scripts/check-wasm-size.sh
• fixed an existing compile issue in contracts/settlement/src/test.rs so the workspace passes clippy and cargo test
• included formatting-only updates required by cargo fmt --all --check

Validation

Ran locally from the workspace root:

• cargo fmt --all
• cargo fmt --all --check
• cargo clippy --all-targets --all-features -- -D warnings
• cargo test
• bash ./scripts/check-wasm-size.sh
• cargo build --target wasm32-unknown-unknown --release -p callora-vault
• stellar contract build --package callora-vault
• cargo tarpaulin --config tarpaulin.toml

WASM size results

• callora-revenue-pool: 21070 bytes
• callora-settlement: 24127 bytes
• callora-vault: 36975 bytes

All publishable contract WASM artifacts are below the 65536 byte Soroban limit.

Coverage

• workspace line coverage: 98.16% (586/597 lines covered)

Security notes

• no contract runtime logic was changed for the WASM-size feature itself
• the release-size enforcement continues to rely on the existing optimized [profile.release] settings in the workspace Cargo.toml
• the script now reduces CI blind spots by automatically covering newly added publishable cdylib contract crates, helping prevent unnoticed size regressions
• the settlement test fix only restores the intended test setup and does not change production contract behavior

[drips-wave]

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

[iammrjude]

@greatest0fallt1me

I am done please review.

All checks are successful