refactor: rename miden-tx-batch-prover crate to miden-batch

[mmagician]

Renames the miden-tx-batch-prover crate to miden-batch, per this discussion on #2998.

[PhilippGackstatter]

LGTM, though not sure a batch crate is meaningful enough given how little it will contain relative to the already large miden-protocol.

[bobbinth]

Looks good! Thank you! I would probably rename the crate to miden-tx-batch to keep it a bit more narrow.

not sure a batch crate is meaningful enough given how little it will contain relative to the already large miden-protocol.

I wonder if there is a good name we can pick that would combine this and the current block-prover crate. Basically, a single crate responsible for aggregating transactions at different levels (batches, blocks).

---

Also, some more general comments about how this could potentially evolve in the future:

With some upcoming changes in the VM, we'll change how proving works a bit. Specifically:

• The user would execute a given program to build something called TraceProvingInputs (potentially, a better name is needed). This object will contain all the data needed to generate a proof.
• Then, the user will send TraceProvingInputs to the prover and will get an ExecutionProof back.

The above step, makes provers "generic" - i.e., the prover doesn't care if it is generating a proof for a transaction, batch, or block - so, the need for dedicated provers goes away.

What we will need are the "executors" - and these would be different for transactions, batches, and blocks.

I believe the only thing currently missing in the VM for this is the ability to serialize TraceProvingInputs. cc @plafer and @huitseeker in case I'm off here.

[plafer]

I believe the only thing currently missing in the VM for this is the ability to serialize TraceProvingInputs. cc @plafer and @huitseeker in case I'm off here.

Created 0xMiden/miden-vm#3235