docs: update public guides

[Mirko-von-Leipzig]

This PR revamps the external/public facing docs to the new distributes sequencer/full node configuration.

I have also:

• Applied formatting and lints in CI.
• Moved the above to ci.
• Changed the doc deployment workflow to only concern itself with that.
• Renamed a bunch of the make compose-x to make local-network-x
• Added a spellcheck tool
  • make typos only checks for known typos, not general purpose spellchecking
  • Its npm based :( but I didn't find much else that's easy
  • Currently only targets these markdown files
  • Might expand it to include code in the future but that's overly noisy for this PR

I still need to do the network operator guide. It does contain content, but that was AI generated and has not had a pass (or three) done on it. Please ignore that section.

I would suggest reviewing using the actual docusaurus server, and not as raw markdown nor the diffs since this is effectively a full rewrite. Also note that the guides use a binary/docker tab split.

make install-tools
cd docs/external                                                                                                                                      
npm ci
npm run start:dev

I'll keep pushing changes until the operator guide is complete as well; but this is a large chunk so having reviews come in would be great.

[Mirko-von-Leipzig]

cc @igamigo who might be interested in the local network setup.

[sergerad]

Just typo / nit

[kkovaacs]

Suggested change

	The local network exports OpenTelemetry traces to Tempo. Grafana is preconfigured with Tempo as a data source, so use
	The local network exports OpenTelemetry traces to Tempo. Grafana is pre-configured with Tempo as a data source, so use

[Mirko-von-Leipzig]

I actually had to triple check this. Turns out both are correct; your suggestion just means you're old is the old school way 😉

[kkovaacs]

Enabling mermaid would allow us to render a much better diagram with a more maintainable representation here:

Suggested change

	```text
	Clients, wallets, applications
	|
	Load balancer
	|
	Public RPC full nodes
	|
	Block/proof subscriptions
	|
	Sequencer
	/ | \
	/ | \
	Validator NTX builder Remote batch/block provers
	|
	Remote tx prover
	Network monitor observes RPC, validator, provers, explorer, faucet, and note transport.
	```
	```mermaid
	flowchart TD
	A["Clients, wallets, applications"] --> B["Load balancer"]
	B --> C["Public RPC full nodes"]
	C --> D["Block/proof subscriptions"]
	D --> E["Sequencer"]
	E --> F["Validator"]
	E --> G["NTX builder"]
	E --> H["Remote batch/block provers"]
	G --> I["Remote tx prover"]

[Mirko-von-Leipzig]

We've used excalidraw diagrams in the past for these; mermaid is maintainable but so ugly 🥲

I'll see once I get there.

[kkovaacs]

Left a few nits and a suggestion but otherwise looks good.

[Mirko-von-Leipzig]

I'm going to merge this, and then open a new PR for the network operator guide.

Once that's complete, only the internal dev docs need updating but that can wait.