bug: Logging in...error: Timeout waiting for authentication to complete on code-server running ubuntu. Q_FAKE_IS_REMOTE=1 should be documented.

### 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

ubuntu

### Expected behaviour

When I try to login using q login on a code server, my login fails after authentication. It tires to redirect to a 127.0.0.1 URL and I get the following message on the terminal: `Logging in...error: Timeout waiting for authentication to complete`

When I do `export Q_FAKE_IS_REMOTE=1 ` then the authentication flow completes successfully. This environment variable should be documented.

### Actual behaviour

Enter `q login`
Choose Q Dev Pro login
Enter the IAM identity center login and region
Complete the login flow in the browser
Login times out: `Logging in...error: Timeout waiting for authentication to complete`

### Steps to reproduce

Enter `q login`
Choose Q Dev Pro login
Enter the IAM identity center login and region
Complete the login flow in the browser

### Environment

```yaml
[q-details]
version = "1.15.0"
hash = "eb8db5c635fc469f3bd94ead16bb4bfb32d7443b"
date = "2025-09-02T17:55:24.095583Z (26d ago)"
variant = "minimal"

[system-info]
chip = "Intel(R) Xeon(R) Platinum 8488C"
total-cores = 2
memory = "15.34 GB"

[system-info.os.linux]
kernel_version = "6.8.0-1039-aws"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 22.04.5 LTS"
version_id = "22.04"
version = "22.04.5 LTS (Jammy Jellyfish)"

[environment]
cwd = "/home/USER/workspace/"
cli-path = "/home/USER/workspace/"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.1.16"
install-method = "unknown"

[env-vars]
PATH = "/home/USER/.local/bin:/home/USER/.local/bin:/home/USER/.local/bin:/home/USER/.local/bin:/usr/lib/code-server/lib/vscode/bin/remote-cli:/home/USER/.nvm/versions/node/v24.7.0/bin:/home/USER/.local/bin:/home/USER/.local/bin:/home/USER/.local/bin:/home/USER/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/USER/.local/bin"
QTERM_SESSION_ID = "2578fe66a5604e0bbc30c2f82b848535"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.15.0"
SHELL = "/bin/bash"
TERM = "screen"
```

Inizia dal punto di ingresso q login e cerca nella documentazione le indicazioni esistenti sull'autenticazione e Q_FAKE_IS_REMOTE. Documenta quando code-server o un'altra sessione Ubuntu remota richiede questa variabile d'ambiente; il lavoro è completo quando il workaround per il login è individuabile e il flusso descritto è chiaro.

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