docs: clean up rpc pages and bridge node guide

[jcstein]

Issue

When attempting to launch a Mocha bridge node, the process failed because some of the listed RPC providers are pruned, and the node required an archival RPC.

Problem

The current RPC lists are confusing and do not clearly indicate which providers are pruned versus archival. As a result, it’s difficult to know which RPC to use for launching different types of nodes.

Proposed Solution

• 1. Clarify RPC lists — Explicitly label which providers are archival and which are pruned.
• 2. Improve guides — Update node launch guides to clearly specify the type of endpoint (pruned vs. archival) required.
• 3. Expand documentation — Add clear instructions for launching both pruned (regular) and archival nodes, including which RPC type is needed for each case.

[jcstein]

related to #2091

Currently, the “community gRPC endpoints” list does not distinguish between pruned and archival nodes. This causes ambiguity around which endpoints can be used for syncing a fresh Bridge Node (BN) vs just submitting transactions.

Proposal:

Automate the categorization of gRPC endpoints in the docs using a simple check: • Query each endpoint for block height = 1. • If the query fails, mark the endpoint as pruned. • If the query succeeds, mark it as archival.

Why this matters: • Pruned nodes are fine for gRPC-based tx submission or maintaining a synced BN. • Archival nodes are required for syncing a new BN from genesis. • Making this distinction clear helps node operators avoid sync errors and confusion.

Tasks: 1. Create an automation script to check each listed endpoint for block height 1. 2. Use the results to split the doc section into: • Archival Endpoints • Pruned Endpoints 3. Add a short explanatory note on the differences and appropriate usage for each.

References:

• Example of pruned endpoint returning no data for height 1: https://full.consensus.mocha-4.celestia-mocha.com/block?height=1