feat(conductor, relayer)!: batch multiple Sequencer blocks to save on Celestia fees

[SuperFluffy]

Summary

Batch mutiple Sequencer blocks into single Celestia blobs to reduce fee payments.

Background

Until now, each Sequencer block was turned into multiple blobs (one for overall sequencer block metadata, and one blob per rollup that had transactiosn in the sequencer block). This wasn't as efficient as it could be because the new compression scheme introduced in #1006 can only come to bear with more bytes to compress.

Relayer will collect sequencer blocks up to a total (compressed) size of 1MB (1/2 of the current max of 2MB that Celestia blocks can be).

Changes

• Introduce protobuf messages astria.sequencerblock.v1alpha1.CelestiaHeaderList and astria.sequencerblock.v1alpha1.CelestiaRollupDataList
• Rename astria.sequencerblock.v1alpha1.CelestiaRollupBlob to astria.sequencerblock.v1alpha1.CelestiaRollupData
• Rename astria.sequencerblock.v1alpha1.CelestiaSequencerBlob to astria.sequencerblock.v1alpha1.CelestiaHeader
• Collect Sequencer Blocks into the *List protobuf messages before posting them to Celestia (instead of splitting up each Sequencer block into mutiple blobs and posting them one by one).

Testing

Add unit tests around the next submission aggregation logic. Update conductor blackbox tests.

Metrics

• CELESTIA_PAYLOAD_CREATION_LATENCY: histogram with microsecond units to track the time it takes to create a payload of Celestia blobs (encoding + compressing all protobufs)
• metrics for reporting compression ratio and total compressed payload size were moved from the payload/blob construction phase to the submission phase.

Breaking Changelist

• Relayer and Conductor write/read new protobuf messages to/from Celestia.

Related Issues

Closes #1042
Closes #1049

[Fraser999]

LGTM - mostly just nitpicks and a couple of questions.

[joroshiba]

I haven't ever loved the naming of these, and I think the new names make it if anything worse.

The core issue is that these are Celestia prefixed but the data has nothing to do with celestia. Especially the new CelestiaHeader is not great because Celestia has headers and have nothing to do with these.

I propose we get rid of the Celestia prefix entirely and have RollupData and SequencerBlockMetadata, and their list forms. The Sequencer Block one is hard because it's the SequencerBlockHeader plus some information. I think metadata encompasses this alright.

[SuperFluffy]

Unfortunately RollupData was already taken in the same protobuf package. I chosen the following nomenclature instead in 401233a:

• SubmittedMetadata: since the full type name is actually astria.sequencerblock.v1alpha1.SubmittedMetadata it's clear that this pertains to a sequencerblock.
• SubmittedRollupData

[SuperFluffy]

@joroshiba I have added a histogram metric CELESTIA_PAYLOAD_CREATION_LATENCY and changed the protobufs to SubmittedMetadata, SubmittedMetadataList, SubmittedRollupData, SubmittedRollupDataList.

[joroshiba]

API approval, new names look good.