Dev container connections lose SecretStore entry on rebuild

Summary

When a workspace connection profile is stored in .vscode/settings.json with a
password field, the extension automatically strips the plaintext password from
the file (expected — plaintext passwords shouldn't be committed). However, when a
Dev Container is rebuilt or VS Code re-establishes the remote connection, the
corresponding SecretStore entry is not present, leaving the connection in a broken
state until the user manually opens the connection editor and re-saves.

Steps to reproduce

1. Add a connection profile to .vscode/settings.json (or check one in) with a
   password field populated.
2. Open the workspace in a Dev Container.
3. Observe the password field is immediately stripped from settings.json by the
   extension (expected behavior).
4. The connection is shown as errored in the extension — it has no password to use.
5. Open the connection editor in the extension UI, make no changes, and click Save.
6. The connection now works (SecretStore entry is created).
7. Rebuild the Dev Container (e.g., to update a dependency or add an extension).
8. After rebuild, the connection is broken again — back to step 4.

Expected behavior

On first activation of a connection profile from workspace settings, the extension
should prompt for the password and store it in SecretStore — or otherwise surface
a clear recovery path — rather than silently leaving the connection in an errored
state. Subsequent cold starts (e.g., container rebuild) should also trigger this
flow if no SecretStore entry exists for the profile.

Actual behavior

The connection is left silently broken. The only workaround is to open the
connection editor and re-save, which is not obvious and must be repeated on every
container rebuild.

Workaround

Open the connection via the extension UI → Edit → Save (no changes needed). This
creates the SecretStore entry and the connection begins working. Must be repeated
after each container rebuild.

Environment

• Extension version: v1.19.0 (pre-release)
• VS Code: remote / Dev Container
• Connection storage: .vscode/settings.json (workspace scope)

Related

• Closes #191 (the connection-storage-in-workspace-settings feature request, now
  shipped — this is a follow-on friction point in the devcontainer flow)
• Related: #143 (password retrieval via custom mechanism)

Beginne mit dem workspace-scoped .vscode/settings.json-Verbindungsablauf und der ersten Aktivierung nach einem Dev Container-Rebuild. Verfolge, wie der Verbindungseditor den SecretStore-Eintrag erstellt und wie die Extension mit einem fehlenden Eintrag umgeht. Die Aufgabe ist erledigt, wenn ein neu erstellter Container entweder zur Eingabe des Passworts auffordert oder einen klaren Wiederherstellungspfad anzeigt und die Verbindung nicht mehr stillschweigend fehlschlägt.