chore(parallel-executor): compressed coin validation

[rymnc]

Linked Issues/PRs

closes #2996

Description

This pull request introduces a new CoinInBatch struct to encapsulate coin-related data and replaces the previous tuple-based representation of coins in the parallel-executor module.

Introduction of CoinInBatch struct:

• crates/services/parallel-executor/src/coin.rs: Added the CoinInBatch struct, which encapsulates coin data such as utxo_id, owner, amount, asset_id, and its variant (Signed or Predicate). Implemented methods for constructing CoinInBatch from CoinSigned and CoinPredicate, as well as conversions to CompressedCoin and Input.

Refactoring to use CoinInBatch:

• crates/services/parallel-executor/src/scheduler.rs: Replaced all instances of (UtxoId, usize) with CoinInBatch in the WorkSessionExecutionResult and WorkSessionSavedData structs, as well as in the CoinDependencyChainVerifier. Updated methods like register_coins_created and verify_coins_used to work with the new struct. [1] [2] [3] [4]

Updates to coin dependency verification:

• crates/services/parallel-executor/src/scheduler.rs: Enhanced the verify_coins_used method to validate coins using the CoinInBatch struct. Added logic to compare CoinInBatch instances with database coins and verify their validity.

Integration of CoinInBatch in batch processing:

• crates/services/parallel-executor/src/scheduler.rs: Updated the get_contracts_and_coins_used function to construct CoinInBatch instances from CoinSigned and CoinPredicate inputs during batch processing. [1] [2]

Module organization:

• crates/services/parallel-executor/src/lib.rs: Added the new coin module to the project and made it accessible within the crate.

Checklist

• Breaking changes are clearly marked as such in the PR description and changelog
• New behavior is reflected in tests
• The specification matches the implemented behavior (link update PR if changes are needed)

Before requesting review

• I have reviewed the code myself
• I have created follow-up issues caused by this PR and linked them here

After merging, notify other teams

[Add or remove entries as needed]

• Rust SDK
• Sway compiler
• Platform documentation (for out-of-organization contributors, the person merging the PR will do this)
• Someone else?

[AurelienFT]

Nice ! It cleans the code + it add the feature. I think we can place this in the skeleton PR as it simplifies the code there also.