fix(binance): expose authority startup mismatch reason

[Pigbibi]

Problem

The live risk authority can reject a runner revision during startup, but the runtime previously collapsed that safe, actionable failure into the generic runtime_startup_failed reason. Operators could not distinguish a fixed authorization binding mismatch while preserving fail-closed startup behavior.

Change

• Project allowlisted live risk authority configuration failures to fixed safe reason codes, including runner_revision_mismatch.
• Add fixed English and Chinese notification text for the runner revision mismatch.
• Keep unknown provider or configuration details generalized, with no raw exception text in notifications.
• Preserve fail-closed startup and execution authorization boundaries; this does not alter permissions, secrets, runtime configuration, or order submission.

Validation

• python3 -m unittest tests.test_main_runtime_error_notification -v: 14 passed.
• Startup diagnostic selection: 2 passed.
• Authority CLI selection: 4 passed.
• git diff --check: passed.
• Ruff baseline comparison: current and HEAD baseline each report 20 pre-existing diagnostics; 0 new diagnostics.

The real loader projection was checked with fixed authority material and runner parameters. A mismatch projects to runner_revision_mismatch; this local check did not constitute a production or complete no-submit cycle. No production runtime, Secret, deployment, merge, or order operation was performed.