Bundle hash for redistribution

[dvush]

Adds bundle hash to redistribution output

output json diff:

<               "Bundle": {
<                 "uuid": "$UUID",
<                 "hash": "$HASH"
<               }
---
>               "Bundle": "$UUID"

[github-actions]

Benchmark results for 763b584

Report: https://flashbots-rbuilder-ci-stats.s3.us-east-2.amazonaws.com/benchmark/763b584-10495ea/report/index.html

Date (UTC)	2024-09-27T17:00:55+00:00
Commit	763b5840f7bc43e2a4315578c56c0c98ab863b62
Base SHA	10495ea9ff3441da93792e9e0ee72abec74e24af

Significant changes

Benchmark	Mean	Status
MEV-Boost SubmitBlock serialization/JSON encoding	-35.85%	Performance has improved.

[ryanschneider]

lgtm! One question though: eventually we want to add additional "metadata" like the sender field as well (which would be either the bundle signing key or the tx sender depending on if the order is only a single tx or not). Do we think we'd continue to add this new metadata to ExtendedOrderId as well? Perhaps we could end up with/ something like:

pub enum ExtendedOrderId {
    Tx { hash: B256, sender: Address },
    Bundle { uuid: Uuid, hash: B256, sender: Address },
    ShareBundle{ hash: B256, sender: Address },
}

And I think ShareBundle might want an tx_hash: Option<B256> for single-tx sbundles (since one of the desires is for end users to be able to lookup their refunds via sent tx hashes, and IIUC private txs get converted to single-tx sbundles).

Anyways not advocating for doing any of this now, just wanted to get the idea down and make sure we're not backing ourselves into a corner by putting the hash in the OrderId!