docs: make rpc and api sections more digestible

[jcstein]

discussion in slack

[jcstein]

This issue should handle:

1. https://github.com/celestiaorg/docs/issues/1743
2. https://github.com/celestiaorg/docs/issues/1465
3. https://github.com/celestiaorg/docs/issues/1598
4. and also make a page in docs with paid RPC services that people can use and historical data providers

[jcstein]

5. https://github.com/celestiaorg/docs/issues/1755

[jcstein]

adding from previous issue: feature request: make an issue template for adding new RPCs

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

this would include

• type of endpoint
• open ports
• verification that it works
• etc...

[jcstein]

RPCs that work for light nodes that are reliable:

Mainnet Beta

Endpoint	Status
rpc.celestia.pops.one	operational
public-celestia-consensus.numia.xyz	operational
consensus.lunaroasis.net	operational
celestia.port-routing.lava.build	WIP

Mocha

Endpoint	Status
rpc-mocha.pops.one	operational
public-celestia-mocha4-consensus.numia.xyz	operational
consensus-full-mocha-4.celestia-mocha.com	operational
full.consensus.mocha-4.celestia-mocha.com	operational
celestiatm.port-routing.lava.build	WIP

[jcstein]

                    ┌───────────────┐
User (REST API)────►│               │
                    │      Node     │
User (OpenRPC)─────►│               │
                    └─────┬─────────┘
                          │
                          │ gRPC
                          │
                      ┌───▼───────────┐
 User (REST API)─────►│               │
                      │      App      │
 User (gRPC)─────────►│               │
                      └─────┬─────────┘
                            │
                            │ Tendermint RPC
                            │
                      ┌─────▼──────────┐
                      │      Core      │
                      └────────────────┘

cc @nashqueue

from #1220

[jcstein]

Update based on responses from Grove team:

Feature	Data Availability Endpoints	Consensus Endpoints
Self-serve setup available	Yes	Yes
Archival endpoints available	Yes	Yes
Non-archival endpoints available	No (only archival)	No (only archival)
Free endpoints available	Yes	Yes
Paid endpoints available	Yes	Yes
Free endpoint limits	100k monthly relays @ 30TPS	100k monthly relays @ 30TPS
Networks supported	Mocha testnet, Mainnet Beta	Mocha testnet, Mainnet Beta

from #1743