Add tooling to compare execution cycles between two MASP packages

Continuation of [protocol-1920](https://github.com/0xMiden/protocol/issues/1920#issuecomment-4121083903)

The goal is comparing the performance of hand-written MASM vs code generated by the compiler.

We have the benchmark for the MASM P2ID note in the protocol repo (see the results at https://github.com/0xMiden/protocol/blob/next/bin/bench-transaction/bench-tx.json). We should replicate at least one scenario in tests/integration-network/src/mockchain/basic_wallet.rs and measure the number of cycles for the Rust version of the P2ID note. Ideally we want the latest numbers posted in an easy to find place (in a README file?).

### Potential follow-up

Use [profiling infra](https://github.com/0xMiden/compiler/issues/965) to report not only total cycle count diffs but also provide insights into where cycles are spent.

Start by examining the existing benchmark for MASM P2ID note in the protocol repo (bench-tx.json). Then look at tests/integration-network/src/mockchain/basic_wallet.rs to replicate a scenario. Use the profiling infrastructure mentioned in issue #965 to measure cycles. The output should be documented in a README file for easy reference.

Scritto dal modello di indicizzazione a partire dal testo della issue.