[FEATURE] Support Per Version Bedrock inference profile ARNs in model picker

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When using Claude Code with AWS Bedrock, the model picker shows distinct options for different model version (e.g. opus 4.1, opus 4.5, opus 4.6, Haiku) However opus versions resolve to the same env variable ANTHROPIC_DEFAULT_OPUS_MODEL, meaning only one Bedrock inference profile ARN can be configured per tier.

This means selecting "opus 4.1" vs opus 4.6" in the picker both hit the same inference profile ARN, making picker non functional for switching between versions of bedrock

Current Behavior:
Model picker shows: opus 4.1, Opus 4.6, etc.
All Opus variants map to ANTHROPIC_DEFAULT_OPUS_MODEL
switching between diff opus version has no effect, both use the same eARN
Users must manually edit settion.json or use shell alias to switch version

Proposed Solution

Each model version in the picker should be configurable with its own Bedrock inference profile ARN.
Example:
ANTHROPIC_DEFAULT_OPUS_41MODEL:arn:aws:.../profile-for-4.1
ANTHROPIC_DEFAULT_OPUS_46MODEL:arn:aws:.../profile-for-4.6

or alternatively,

{
"bedrockModelMap": {
"claude-opus-4-1": "arn:aws:.../profile-for-4.1"
"claude-opus-4-6": "arn:aws:.../profile-for-4.6"
:}
}

Alternative Solutions

or alternatively,

{
"bedrockModelMap": {
"claude-opus-4-1": "arn:aws:.../profile-for-4.1"
"claude-opus-4-6": "arn:aws:.../profile-for-4.6"
:}
}

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_