feat(run-morph-node): support centralized sequencer configuration

[curryxbo]

Background

Node operation is moving to the centralized sequencer architecture. run-morph-node (the scripts / configs / compose setup used to run a Morph node) needs to be adapted so operators can run nodes correctly against the centralized sequencer.

Goal

Update run-morph-node so that, out of the box, it can launch and operate a node in centralized-sequencer mode with correct defaults.

Scope / Tasks

• Add/adjust configuration (flags, env vars, config files) required for centralized-sequencer mode.
• Provide config presets/profiles for the relevant node roles (sequencer vs. follower/verifier) as applicable.
• Update startup scripts / docker-compose / images to wire the new configuration.
• Set sane defaults and validate required parameters on startup.
• Verify a node started via run-morph-node syncs and operates correctly against the centralized sequencer on devnet/testnet.
• Update the in-repo README/usage notes; keep aligned with morph-doc (see companion issue).

Acceptance Criteria

• run-morph-node can start a working node in centralized-sequencer mode with documented configuration.
• Behavior matches the updated morph-doc node operation guide.

Related

• Companion issue: morph-doc node operation guide for centralized sequencer.

[curryxbo]

Implemented in run-morph-node PR morph-l2/run-morph-node#100 (single node startup + DERIVATION_VERIFY_MODE; sequencer contract / consensus switch height left to the binary's per-network hard-coded defaults).