share: ensure DA for heights for which the data was requested

[Wondertan]

We currently serve data and do DAS independently, but it may be possible to serve shares or blobs without checking DA for the particular height. We should change that and block calls like GetSharesByNamespace and all the BlobModule getters until the data is available via the SharesAvailable call.

For context, this was part of various sync discussions and finally came out on the lower level in Rollkit rollkit/rollkit#986 (comment)

[Wondertan]

We should be careful with all the SharesAvailable implementations we have for diff node types we use. We need to audit that for possible locking issues this may create in this code path

[Wondertan]

Well, it needs #1595, because it implies the SharesAvailabe is regularly called by our users and the DASer, but we don't want to have parallel data requests.

[musalbas]

We should change that and block calls like GetSharesByNamespace and all the BlobModule getters until the data is available via the SharesAvailable call.

This behaviour shouldn't be mandatory, it should be optional. There are valid use cases for getting data before DASing in completed. For example, a sequencer might want to get a head-start in making the next block, or they might be happy being a super-light client (which is still better than relying on a centralized RPC endpoint which is what Ethereum sequencers do now).