Request a way to customize api.retries, possibly combined with some sort of exponential backoff configuredx

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 26.3.1 (25D2128)

### Expected behaviour

being able to retry more times

### Actual behaviour

Limited to 3 retries with no way to configurex

### Steps to reproduce

yes

### Environment

```yaml

[q-details]
version = "1.28.3"
hash = "2eaf2e5262c5201a8bba63d8a244f1b8d8fb9ff8"
date = "2026-03-28T17:32:21.180959Z (2d ago)"
variant = "full"

[system-info]
os = "macOS 26.3.1 (25D2128)"
chip = "Apple M3 Pro"
total-cores = 12
memory = "36.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/Users/USER/.toolbox/tools/toolbox/1.1.3887.0/toolbox-exec"
shell-version = "5.9"
terminal = "iTerm 2"
install-method = "toolbox"

[env-vars]
PATH = "/Users/USER/workspace/MeshClaw/src/MeshClaw/bin:/Users/USER/.aim/mcp-servers:/Users/USER/.config/smithy-mcp/mcp-servers:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/pmk/env/global/bin:/Library/Apple/usr/bin:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.toolbox/bin:/Users/USER/bin"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"
```

L’issue non indica file né test. Inizia individuando dove api.retries è definito e applicato nella CLI, quindi esamina la configurazione e i test di retry esistenti; il lavoro è completato quando gli utenti possono configurare il numero di retry e il comportamento di retry o backoff concordato è coperto dai test.

Scritto dal modello di indicizzazione a partire dal testo della issue.