Console: fix setup content that contradicts the gateway

[swarna1101]

These fixes are in optimum-cross-functional-dashboard. They are tracked here because the docs can't be correct while Console shows a different command.

Fix

• components/dashboard/screens/Signal.tsx. The run command is hardcoded as OPTIMUM_ENROLLMENT_KEY … ghcr.io/getoptimum/optimum-gateway:latest, which is wrong. Use gatewayRunCommand() instead.
• lib/signalSetup.ts.
  • Correct the per-client flags: Prysm --peer, Lighthouse --boot-nodes plus --trusted-peers, Teku --p2p-direct-peers, Nimbus --direct-peer, Lodestar trusted/direct peer.
  • Replace the "0 of 8 peers / TCP 13000" failure text with the real failures on ports 33212 and 33213.
• lib/gatewayRunCommand.ts.
  • Add the identity volumes.
  • Pin the image version instead of :latest.
  • Pass a real config instead of -config "". Not done, deliberately: the flag defaults to config/app_conf.yml, which is not in the image, so the gateway exits on "unable to load config" before reading any environment variable. Everything Console sets travels by environment, and a mounted config is a step the operator has to perform before the command can be pasted at all. Verified against the v1.3.2 image: it starts with -config "" and reads its environment.
• components/onboarding/ConnectGatewayStep.tsx. The fallback text says OPTIMUM_ENROLLMENT_KEY; change it to OPT_JOIN_KEY.
• Signal Verify step. It is currently disabled. Wire it to /health and /api/v1/self_info, or remove it from the docs.
• Reports for self-serve accounts. performanceNav returns nothing for self-serve accounts, so the journey's step 10 ("first report") is unreachable.
• Prod feature flags. Turn on self-serve signup, the self-serve role, Signal and Accelerate for launch.

Done when

The command Console generates runs as-is on a clean machine, and matches the Signal docs (#49).

[linear-code]

OPT-1121