bug: `--announce-only` is silently dropped in stake/liquidity/crowd commands

[bitloi]

Several CLI commands accept --announce-only but never actually use it — the flag is parsed and validated, then silently dropped before reaching the downstream command functions.

This means users passing --proxy --announce-only get a normal extrinsic execution instead of a proxy announcement, with no warning that the flag was ignored.

Affected commands include stake (add, remove, move, transfer, swap), liquidity (add, remove, modify), crowd (create, contribute, withdraw, finalize, update, refund, dissolve), and others like wallet set-id, wallet associate-hotkey, sudo set, subnets create, etc. — 37 CLI methods in total.

The underlying extrinsic API (sign_and_send_extrinsic) / sign_and_send_batch_extrinsic) already supports announce_only, but full announce-only UX (branched success messaging, slippage disclaimers) hasn't been implemented yet. Until that's done in v10, these flags should be removed so users aren't misled by a non-functional option.

[thewhaleking]

This will be part of v10

[bitloi]

PR #899 removed --announce-only from stake, liquidity, and crowd commands because the flag was accepted but the UX wasn't ready — success messages said things like "Stake added" even though only a Proxy.announce was submitted.

To bring --announce-only back for these commands, the success handling needs to be reworked so that:

• Success messages say "Announcement submitted" instead of implying the operation already completed
• Slippage/rate tables include a note that displayed values are based on current state and may differ when the call actually executes

This applies to stake add/remove/move/transfer/swap, liquidity add/remove/modify, and the crowd operations. Each command has its own output formatting so it needs to be handled per command.

Currently only wallet transfer and proxy kill support --announce-only.