[codex] Localize IBKR strategy names and document runtime profile status

[Pigbibi]

What changed

• switched IBKR human-facing strategy labels to localized display names in notifications and runtime report summaries
• exposed strategy display names through runtime settings and structured report fields
• refined strategy loader and runtime wiring so adapter inputs and artifact-derived paths come from the runtime contract
• documented the IBKR profile status matrix and added a local status inspection script

Why

• IBKR notifications were showing raw engineering profile ids instead of readable strategy names
• the runtime path and artifact wiring had evolved, but the local tooling and docs had not fully caught up
• operators need a simple way to inspect eligible versus enabled profiles locally

Impact

• Telegram and human-readable logs are cleaner and localized
• machine-facing strategy_profile is still preserved
• local tooling now exposes current IBKR profile status cleanly

Root cause

• display metadata and runtime or artifact metadata were spread across different places, so human-facing output and local operator tooling lagged behind the current runtime model

Validation

• tests/test_runtime_config_support.py tests/test_rebalance_service.py tests/test_request_handling.py passed locally (34 passed)
• tests/test_strategy_loader.py tests/test_strategy_runtime.py passed locally (9 passed)
• scripts/print_strategy_profile_status.py --json ran successfully with the required local dependencies