bug(desktop): upgrading to 0.5.2 resets/drops connected remote hosts

Description

After updating the macOS desktop app from 0.5.1 to 0.5.2 (via in-app updater), previously configured connected remote hosts and active workspace context disappeared from the sidebar and UI view.

Upon inspecting the filesystem and daemon status:

1. ~/.paseo/config.json is intact and contains all custom profiles and settings.
2. The local daemon continues running fine, and remote daemons (on other servers) are healthy.
3. However, the desktop app's renderer state / IndexedDB (~/Library/Application Support/Paseo) appears to have reset/cleared the saved remote host connections during the 0.5.2 update/migration (legacyRendererSettingsImported), presenting an empty/initial state to the user without preserving connected remote daemons.

Steps to Reproduce

1. Run Paseo desktop app 0.5.1 on macOS with several connected remote daemons / hosts.
2. Update Paseo desktop app to 0.5.2 (via in-app update).
3. Restart the app.

Expected Behavior

Remote hosts and previously connected daemons should persist across application updates.

Actual Behavior

Connected remote hosts are wiped from the client list, requiring the user to manually re-add each remote server.

Environment

• OS: macOS 15.x / Darwin (Apple Silicon)
• Paseo Desktop Version: 0.5.2
• Daemon Version: 0.5.1 / 0.5.2