feature request for file extension '.q' for promts

### 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.7.1 (24G231)

### Expected behaviour

I would like to raise a feature request so that '.q' can be used to run prompts as scripts.

### Actual behaviour

This is not yet implemented.

### Steps to reproduce

Functionality does not exist.

### Environment

```yaml

[q-details]
version = "1.17.1"
hash = "b0ef39f91625c36c2ed6f065628e7165fae9012c"
date = "2025-09-30T22:01:25.726592Z (5d ago)"

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

[environment]
cwd = "/Users/USER/git/infrastructure-services/device42/d42_client/d42_client"
cli-path = "/Users/USER/git/infrastructure-services/device42/d42_client/d42_client"
install-method = "brew"

[env-vars]
PATH = "/Users/USER/localenv/bin:/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:/usr/local/MacGPG2/bin:/Applications/Wireshark.app/Contents/MacOS:/Applications/VMware Fusion.app/Contents/Public:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.local/bin:/Users/dklein/.local/bin:/Users/USER/.local/bin"
QTERM_SESSION_ID = "ef592a5e7b2349a99b926b2fd2d36376"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.14.1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"
```

Inizia esaminando come CLI esegue attualmente i prompt, quindi confronta questo percorso con i comandi q doctor e q restart menzionati nel report. Il lavoro è completo quando il comportamento per l’uso dei file .q come script di prompt è stato definito e implementato, compreso il modo in cui vengono invocati e quale output o quali errori devono ricevere gli utenti.

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