Re-authenticating drops the user input and chat history

## Problem

## Steps to reproduce the issue

1. Open Amazon Q side panel on VSCode and wait for the auth session to be expired
2. On the "Ask a question" input, carefully type the most beautiful prompt you ever typed
3. Send the message
4. You get the "Session expired - Select a profile" button and message
5. Click on the button to renew your session and accept the login
6. The chat reloads totally empty
7. Your wonderful prompt is lost forever, and potentially all the history of context of the discussion you were having with Q 🥲

## Expected behavior

1. Open Amazon Q side panel on VSCode and wait for the auth session to be expired
2. On the "Ask a question" input, carefully type the most beautiful prompt you ever typed
3. Send the message
4. You get the "Session expired - Select a profile" button and message
5. Click on the button to renew your session and accept the login
6. The chat reloads on the state it had before (conversation history + typed message)

## System details (run `AWS: About` and/or `Amazon Q: About`)

````
OS: Darwin arm64 24.5.0
Visual Studio Code extension host: 1.100.3
Amazon Q: 1.72.0
node: 20.19.0
electron: 34.5.1
```

No source files or tests are named. Start by reproducing the expired-session flow in the Amazon Q side panel on VS Code and trace the authentication renewal and chat reload entry points. Done means the pre-renewal conversation history and unsent prompt remain after accepting the login.

Written by the indexing model from the issue text.