[Bug]: Workspace setting for `python.defaultInterpreterPath` set every time extension loads

### Describe the bug

When this extension is active, the `python.defaultInterpreterPath` setting in the workspace (`.vscode/settings.json`) is set to the ArcGIS Pro Python binary. For ArcGIS Pro-related projects, this can make sense. However, on non-ArcGIS Python projects, or non-Python projects, this is typically unwanted and can introduce noise in source control.

### To Reproduce

1. Install ArcGIS Pro Debugger extension.
2. Open a blank workspace.
3. Trust the workspace to activate extensions.

A new `.vscode/settings.json` file is created with the following contents:

```json
{
"python.defaultInterpreterPath": "C:\\Program Files\\ArcGIS\\Pro\\bin\\Python\\envs\\arcgispro-py3"
}
```

### Expected behavior

Extensions should not inject settings for every workspace by default. I believe this behavior should be gated behind a confirmation prompt or setting.

### Additional context

_No response_

### ArcGIS Pro Debugger extension version

1.2.3

### ArcGIS Pro info

{'LicenseLevel': 'Advanced', 'InstallDir': 'c:\\program files\\arcgis\\pro\\', 'Installer': 'danielm', 'ProductName': 'ArcGISPro', 'Version': '3.7.1', 'SourceDir': 'C:\\Users\\danielm\\Documents\\ArcGIS Pro 3.7\\ArcGISPro\\', 'InstallType': 'N/A', 'BuildNumber': '1901', 'InstallDate': '2026-07-17', 'InstallTime': '14:11:12', 'SPNumber': 'N/A', 'SPBuild': 'N/A', 'LicenseType': 'Named User'}

Reproduce activation in a trusted blank workspace and inspect the generated .vscode/settings.json. Trace the extension entry point that writes python.defaultInterpreterPath, then verify that activation no longer injects the setting into unrelated workspaces unless the intended opt-in behavior is used.

Written by the indexing model from the issue text.