conductor: fetch sequencer and rollup blobs from celestia in one RPC

[SuperFluffy]

At the moment conductor first fetches sequencer data for a given height, followed by its rollup data. That is unecessary since we can fetch both at in one blob.GetAll RPC.

[noot]

does your PR #487 fix this?

[noot]

closing as it's implemented

[SuperFluffy]

This is not yet implemented. We are currently first fetching the blobs in the sequencer namespace followed by a separate fetch of the desired rollup namespace:

1. fetching the CelestiaSequencerBlob:

   astria/crates/astria-conductor/src/data_availability/mod.rs

   Line 274 in aae161b

   .get_sequencer_blobs(height, sequencer_namespace)

2. fetching the CelestiaRollupBlob:

   astria/crates/astria-conductor/src/data_availability/mod.rs

   Line 440 in aae161b

   .get_rollup_blobs_matching_sequencer_blob(height, rollup_namespace, &blob)

[SuperFluffy]

It turns out that Celestia does not quite allow our use case: blobs for several namespaces at a given height can be fetched if and only if there exist blobs for all namespaces at that height. For example, if we desire to fetch blobs for namespaces foo and bar at Celestia height 10 and a blob at bar does not exist, then blob.GetAll will return an error, see this issue: celestiaorg/celestia-node#3292
Closing the issue because we will not be able to implement it for the foreseeable future.