UX improvements for Blobstream

[rach-id]

Now that we're rolling Blobstream to mocha and eventually mainnet in upcoming weeks/month, the following issues would be nice to have to make it easier for developers to use Blobstream and have good UX:

1. Move the proofs generation that we're doing in core and app to celestia-node so that rollups can query the proofs from their light nodes instead of having RPC endpoint etc. Also, would help in having only the height and blob commitment in rollup header instead of now needing also the transaction hash. Move proving of inclusion to Blobstream data commitments to celestia-node celestia-app#2713
2. Support proving blob commitment subtree roots in Blobstream so that users don't have to send the actual shares to verify their inclusion. Support proving subtree roots blobstream-contracts#258
3. Create a test environment for rollup devs that they can spin up easily with an example sequencer and verifier. This would allow them to just start writing code and experimenting before rewriting everything as they see fit. Developer test environment #613
4. Support inclusion verification for BlobstreamX since it uses different batch sizes, nonces etc, we will need to adapt our logic to that. I still did not create an issue for this since I'm still not sure how this would look like (whether we would have this logic in app or node and how would the production ready Blobstream X contract would look like)
5. Return error codes in the binary merkle tree implementation. return error codes in the binary merkle tree implementation blobstream-contracts#266
6. Have a specialised L2 Blobstream contract and eventually BlobstreamX so that it's cheaper to deploy (I don't think it's worth worrying about now).
7. Add support for some monitoring for Blobstream orchestrator, and Blobstream/BlobstreamX relayer so that node operators can have more information. QGB monitor confirms attestations #3

It would be good if we could get some feedback from users so that we can define the priorities for each task.