Add flag to use random addresses for proof_generator_addr in Aligned CLI

Description

This PR adds a flag to set every proof_generator_address with a random value.

How to test

Run aligned fast mode

1. make anvil_start_with_block_time
2. make aggregator_start
3. make operator_full_registration CONFIG_FILE=config-files/config-operator-1.yaml
4. make operator_start CONFIG_FILE=config-files/config-operator-1.yaml
5. make batcher_start_local
6. make install_aligned_compiling

Once you have the system running, send proofs using the following command

rm -rf ./aligned_verification_data/ &&
aligned submit \
--proving_system GnarkPlonkBn254 \
--proof ./scripts/test_files/gnark_plonk_bn254_script/plonk.proof \
--public_input ./scripts/test_files/gnark_plonk_bn254_script/plonk_pub_input.pub \
--vk ./scripts/test_files/gnark_plonk_bn254_script/plonk.vk \
--network devnet \
--rpc_url http://localhost:8545 \
--random_address \
--repetitions 8

Once you the batch has been sent, send a new batch of proof using the same command

You should see that there were created two batches with the same amount of proofs with different merkle roots

Type of change

• Bug fix

Checklist

• “Hotfix” to testnet, everything else to staging
• Linked to Github Issue
• This change depends on code or research by an external entity
  • Acknowledgements were updated to give credit
• Unit tests added
• This change requires new documentation.
  • Documentation has been added/updated.
• This change is an Optimization
  • Benchmarks added/run
• Has a known issue
  • Link to the open issue addressing it
• If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
  • This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
  • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible