[Advancement] Unify multi-network context switching with safety confirmations

[Nanle-code]

Objective

Improve multi-network context switching with explicit confirmations when moving from test to public networks.

Target area

multi_network command

Context

Accidental mainnet context is a severe footgun; confirmations and clear prompts reduce risk.

Requirements

• Show current network prominently in prompts for dangerous ops
• Require confirmation when switching to mainnet
• Persist last-used network per project when configured

Acceptance criteria

• Mainnet switch requires confirmation in interactive mode
• JSON mode exposes network identity fields
• Tests cover confirmation bypass rules

Pull request merge requirements

Pull requests that resolve this issue must not be merged until all of the following are true:

1. All required CI checks are green on the latest commit of the PR (build, tests, lint/format, and any workflow jobs required by branch protection).
2. The branch has no merge conflicts with the target branch (master / default), and a clean merge or rebase is possible without unresolved conflicts.
3. Review feedback is addressed, and the change remains focused on this issue’s acceptance criteria.

Contributors should run the local CI-equivalent checks before opening or updating the PR (see CI_ENFORCEMENT.md and CONTRIBUTING.md).

[abbaskachia]

@abbaskachia has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on issue #808.

I’ll improve the "multi_network" command so network context changes are explicit and safer, particularly when moving from test networks to mainnet.

My plan is to:

• Display the current network prominently in prompts for operations where network identity matters.
• Require an explicit confirmation before switching to mainnet in interactive mode.
• Preserve the expected non-interactive/JSON behavior without introducing an interactive prompt where it is not appropriate.
• Expose clear network identity fields in JSON mode.
• Persist the last-used network per project when the configuration option is enabled.
• Add focused tests covering mainnet confirmation, confirmation bypass rules, JSON output, and persisted network context.
• Handle invalid or unsupported network configurations cleanly.
• Run the local CI-equivalent checks documented in "CI_ENFORCEMENT.md" and "CONTRIBUTING.md".

I’ll keep the implementation focused on the "multi_network" command and ensure the branch is conflict-free and all required CI checks pass before requesting merge.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abbaskachia to this issue.