feat: add MiniMax Messages-compatible route

[octo-patch]

Reason: add target provider/model to existing provider registry

Summary

• Add a built-in MiniMax Messages-compatible route across the provider registry, configuration, CLI, TUI, and request client.
• Register MiniMax-M3 and MiniMax-M2.7 with model capabilities, context metadata, and supported pricing fields.
• Document global and China endpoints for both supported protocols and refresh generated web facts from their source.

Testing

• cargo check -p codewhale-config -p codewhale-agent -p codewhale-tui -p codewhale-cli --all-targets
• cargo test -p codewhale-config minimax -- --nocapture
• cargo test -p codewhale-agent minimax -- --nocapture
• cargo test -p codewhale-tui --bin codewhale-tui minimax -- --nocapture
• cargo test -p codewhale-cli parses_auth_subcommand_matrix -- --nocapture
• cargo clippy -p codewhale-config -p codewhale-agent -p codewhale-cli --all-targets -- -D warnings
• cargo fmt --all -- --check
• node web/scripts/check-facts.mjs

Checklist

• Updated docs or comments as needed
• Added or updated tests where relevant
• Verified TUI behavior manually if UI changes
• Harvested/co-authored credit uses a GitHub numeric noreply address

[github-actions]

Thanks @octo-patch for taking the time to contribute.

This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered.

Please read CONTRIBUTING.md for the expected contribution shape. A maintainer can grant recurring PR access by commenting /lgtm on a pull request.