Don't include blobs in chain info query responses

[ndr-ds]

#2220 (comment)

[ndr-ds]

We need to make it so that you can't have a ChainInfoQuery return more than 1 of the following 3 at the same time:

• ChainManager's proposed -> should be fine to return the whole BlockProposal after we add the limits on Fix storage DOS attack in block proposals #2199
• ChainManager's proposed_blobs -> Same as above
• ChainManager's locked_blobs -> This one might have published and read blobs, so we need to implement a custom way of returning the locked blobs: maybe sending the blobs one by one and the caller can aggregate them. This could technically also be solved by streaming the blobs as the response.

[afck]

Yes, I think the ChainInfoQuery should have a field like request_locked_blob: Option<BlobId> or maybe request_locked_blobs: Vec<BlobId>.

[ndr-ds]

We could technically do request_locked_blobs and calculate how many we can request at once based on the current blob size limit and gRPC message size limit 🤔 so we minimize the amount of chain info queries we do