Amazon Q fails to activate on Remote SSH with "Cannot redefine property: default" error after previously working correctly

## Problem
Amazon Q extension keeps loading indefinitely in VSCode when connected to a Remote SSH server. The extension fails to activate with a TypeError: "Cannot redefine property: default". This issue started occurring recently, as the extension was working properly before.

## Steps to reproduce the issue

1. Connect to a remote server using VSCode Remote SSH extension
2. Wait for VSCode to initialize on the remote server
3. Observe that Amazon Q extension shows a loading indicator and never completes initialization
4. Check VSCode logs to see the following error:

## Expected behavior
Amazon Q should initialize properly and be available for use when connected to a remote server via SSH, just as it does in local VSCode instances and as it did previously on this same setup.

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

- OS: Linux (Remote SSH server)
- Visual Studio Code version: Using VS Code Server (Stable-17baf841131aa23349f217ca7c570c76ee87b957)
- AWS Toolkit version: Not available due to extension loading failure
- Amazon Q version: 1.63.0
- Additional context:
- The extension was working correctly on this same setup previously and started exhibiting this issue recently without any known changes to the environment

Start by reproducing the failure with VS Code Remote SSH on the listed Linux server and inspect the VS Code logs for the activation error. Use the AWS: About or Amazon Q: About commands when available, and consider the issue done when Amazon Q activates successfully in the remote session without the loading indicator.

Written by the indexing model from the issue text.