Add simple progress indicator for long-running operations

### 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 15.5.0 (24F74)

### Expected behaviour

Show a simple progress bar ([████████░░] 80%) or percentage (80%) for operations that take more than 2-3 seconds to complete. The indicator should update in place without creating scrolling text and clear when the operation finishes.

### Actual behaviour

> a simple progress indicator would be much better than verbose status messages. A clean `[████████░░] 80%` or just `80%` would give users the feedback they need without cluttering the interface.

This would be especially useful for:
- AWS CLI calls that take time (large resource queries)
- File operations on big directories
- CDK/Terraform operations
- MCP server tool calls

The implementation could be as simple as:
- Show progress inline where the cursor is
- Update in place (no scrolling text)
- Clear when complete
- Maybe just show for operations taking >2-3 seconds

Would you like me to help you submit this as a feature request to the Q team? A minimal progress indicator like this would be a great UX improvement without adding complexity.
[Tool uses: none]

> either of those would be fantastic!

Perfect! Let me help you submit this feature request to the Q team.
[Tool uses: report_issue]

(...truncated)
```

### Steps to reproduce

_No response_

### Environment

```yaml

[q-details]
version = "1.13.0"
hash = "7dee6efdf68f6343e80a56028e6b40f8eff77746"
date = "2025-07-31T02:57:26.581678Z (2d ago)"

[system-info]
os = "macOS 15.5.0 (24F74)"
chip = "Apple M1 Pro"
total-cores = 10
memory = "32.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/.local/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/USER/.toolbox/bin:/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:/usr/local/go/bin:/Users/USER/.local/bin:/Users/USER/.cargo/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/opt/homebrew/opt/fzf/bin"
QTERM_SESSION_ID = "2579b8b0ed8d41d59c4133fc2f0a9ede"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.13.0"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
ZDOTDIR = "/Users/USER"
__CFBundleIdentifier = "com.microsoft.VSCode"

[chat-settings]

[chat-trusted_tools]
@awslabs.core-mcp-server/prompt_understanding=trusted
execute_bash=trusted
@q-session-manager/save_session=trusted
@q-session-manager/get_startup_context=trusted
@amzn-mcp/edit_quip=trusted
@amzn-mcp/create_quip=trusted
fs_read=trusted
fs_write=trusted

[chat-failed_request_ids]
none

[chat-context]
current_profile=q_cli_default
profile_context=
AmazonQ.md
README.md
.amazonq/rules/**/*.md

files=none
```

Das Issue nennt keine Dateien, Tests oder Einstiegspunkte. Beginne damit nachzuverfolgen, wie die CLI lang laufende AWS-, Datei-, CDK/Terraform- und MCP-Operationen rendert, und definiere dann eine abgegrenzte Operation sowie das Verhalten des Terminals, die validiert werden sollen; abgeschlossen ist die Arbeit, wenn Fortschrittsaktualisierungen an Ort und Stelle erfolgen und bei Abschluss sauber verschwinden.

Vom Indexierungsmodell aus dem Issue-Text verfasst.