Bedrock + Opus 4.7 still fails with thinking.type.enabled error (v1.0.107)

## Summary

Follow-up to #1225. The Bedrock path (`use_bedrock: true`) still sends the
legacy `thinking.type.enabled` parameter to Opus 4.7 and fails with HTTP 400.

The v1.0.99 fix appears to only have addressed the direct Anthropic API path.
Bedrock users on Opus 4.7 are still broken as of v1.0.107.

## Reproduction

Workflow:
```yaml
- uses: anthropics/claude-code-action@v1.0.107
with:
use_bedrock: "true"
claude_args: |
--model arn:aws:bedrock:ap-northeast-1::application-inference-profile/
--max-turns 100
```

The Application Inference Profile points to `global.anthropic.claude-opus-4-7`.

## Error

```
SDK execution error: ...
API Error: 400 {"type":"error","error":{"type":"invalid_request_error",
"message":"\"thinking.type.enabled\" is not supported for this model.
Use \"thinking.type.adaptive\" and \"output_config.effort\" to control thinking behavior."}}
```

User-agent in upstream logs: `claude-cli/2.1.119 (external, claude-code-github-action)`

## Environment

- Action: `anthropics/claude-code-action@v1.0.107`
- Provider: AWS Bedrock (ap-northeast-1)
- Model: `global.anthropic.claude-opus-4-7` (via Application Inference Profile)
- Agent SDK: 0.2.113 (bumped in v1.0.100 per release notes)

## Expected

Action should send `thinking.type.adaptive` for Opus 4.7 over Bedrock,
matching the fix already applied to the direct Anthropic API path.

## Workaround

Pinning Bedrock Application Inference Profiles back to Opus 4.6.

Start at the Bedrock path selected by use_bedrock: true and compare its request construction with the direct Anthropic API fix from v1.0.99. Reproduce the v1.0.107 workflow using the Opus 4.7 Application Inference Profile and verify that the request uses adaptive thinking and no longer returns the reported HTTP 400 error.

Written by the indexing model from the issue text.