Add justification to batches, progress on validation pipeline

[nomaxg]

This PR introduces:

• justification to Arbitrum batches which will be validated against the HotShot commitment corresponding to the batch
• A series of host-io changes to the wasm validation pipeline that allows the wasm executable to read a hotshot commitment (currently, these default to [0; 32] in many places to ensure backwards compatibility)

Future work:

• Tests
• Add logic to fetch the HotShot commitment from a live contract (this is currently mocked)
• Set Espresso flags correctly in the espresso variant of nitro-testnode

Depends on:
EspressoSystems/geth-arbitrum#2

To test (for backwards compatibility):

./test-node.bash --dev --init
./test-node.bash script send-l2 --to address_0x673C9b46952080D3bf1B8d689C7BBC590a8755Cb --ethamount 5 --l2url
# spin up validation nodes
docker compose up validation_node
docker compose up validator

[sveitser]

LGTM

[sveitser]

I'm getting this failure locally for make test-go

=== Failed
=== FAIL: broadcaster ExampleBroadcastMessage_broadcastfeedmessage (0.00s)
=== RUN   ExampleBroadcastMessage_broadcastfeedmessage
got:
{"version":1,"messages":[{"sequenceNumber":12345,"message":{"message":{"header":{"kind":0,"sender":"0x0000000000000000000000000000000000000000","blockNumber":0,"timestamp":0,"requestId":"0x0000000000000000000000000000000000000000000000000000000000000000","baseFeeL1":0,"justification":null},"l2Msg":"3q2+7w=="},"delayedMessagesRead":3333},"signature":null}]}
want:
{"version":1,"messages":[{"sequenceNumber":12345,"message":{"message":{"header":{"kind":0,"sender":"0x0000000000000000000000000000000000000000","blockNumber":0,"timestamp":0,"requestId":"0x0000000000000000000000000000000000000000000000000000000000000000","baseFeeL1":0},"l2Msg":"3q2+7w=="},"delayedMessagesRead":3333},"signature":null}]}

DONE 463 tests, 1 skipped, 1 failure in 117.090s
make: *** [Makefile:327: .make/test-go] Error 1

[ImJeremyHe]

macro error! is used only for once, I think it is better to expand it here and remove the macro.

[ImJeremyHe]

Could you please help me understand this a bit better?

[nomaxg]

Yes, essentially what we are doing is validating that espresso batches (which currently map 1-to-1 to arbitrum batches) correspond to a valid hotshot commitment. This function implements a host-io function that reads a hotshot commitment, so that the wasm layer can pass a commitment to ProduceBlock