cli/wallet: eliminate the ogmigo OgmiosChainContext genesis-config ws-1006 warning

[jmgilman]

Symptom

During host-side wallet funding (yacd wallet topup/add), a non-fatal warning prints before the transaction is built:

OgmiosChainContext: GenesisParams: failed to get genesis config: failed to read json response: websocket: close 1006 (abnormal closure): unexpected EOF

The transaction still builds, signs, submits, and confirms on-chain — this is cosmetic noise, not a failure (observed during the v0.2.0 yacd devnet validation: tx confirmed despite the line).

Cause

Apollo's OgmiosChainContext (via ogmigo) fetches the genesis config over a WebSocket during chain-context init and logs a hardcoded warning to stdout when that fetch closes abnormally (ws-1006). YACD only needs protocol parameters / UTxOs for tx building, not the full genesis config.

Current mitigation

cli/internal/cli/wallet_fund.go routes the offending process stdout to stderr (redirectStdoutToStderr()) so it never corrupts --json output. The warning still appears on stderr during normal runs.

Options to resolve

• Upgrade ogmigo and check whether the genesis-config fetch / warning is fixed or suppressible upstream.
• Move the chain-context off ogmigo (e.g., a Kupo-only UTxO + Ogmios protocol-params path) so the genesis-config fetch is never attempted.
• Suppress the specific warning at the source if the library exposes a logger/option.

Notes

Out of scope for the faucet-removal re-architecture (P1–P5); filed as the durable follow-up noted in the P5 plan. Non-blocking.