docs: document snapshots and historical data providers

[jcstein]

Kyve from #1755

Summary

Kyve has bigquery dataset and RPC for historical access that should be documented.

Details

"I wanted to share the final integration of the Celestia blob and app data with our KYVE Trustless API Endpoint. It supports the blob.Get and the blob.GetAll query as well as block and block_results. For example, you can now query This blob through the Trustless API like this https://staging-613b8d89-data.services.kyve.network/celestia/Get?height=799489&namespace=AAAAAAAAAAAAAAAAAAAAAAAAAMod4SqXFNgavI8=&commitment=FlQmmPb3LYF0hLNd9YQfi9sRb42TKMfXh4KBtBa4BmA=

We have also published all of the Celestia Data on BigQuery and already have users subscribing to them."

Proposed solution

Create a dedicated page for historical data access. Pull out the "production" endpoints from network pages and include them in this page, too.

Please use the Trustless API production endpoint instead: https://data.services.kyve.network/#/celestia

polkachu snapshot from #1598

similar to #1465, add https://polkachu.com/archive_snapshots/celestia consensus archive snapshot to docs

also others from Slack:

https://celestia-tools.stavr.tech/bridge/
https://docs.services-ernventures.com/testnets/celestia/api-snapshot-addrbook#for-bridge-node-v0.18.2-mocha
https://itrocket.net/services/testnet/celestia/#snap-bridge

kingsuper #1465

https://kingsuper.org/snapshots/celestia-bridge-mainnet - note that it is a community snapshot, and not archival

also add kingsuper to consensus nodes if it's not already there, at least a link to the site

[hexmark21]

Hey @jcstein, I would like to work on this issue (and #1598 too). We developed celestia-snapshot-finder and maintain celestia-snapshots repository with fresh, verified snapshots. We plan to add more. Would love to include these along with the other providers - do you have any preferences for how this should be structured in the docs?