BUG: Backup/restore binary tool path (mysqldump, pg_dump, etc.) not persisted between sessions

Describe the bug The binary tool path set during a backup or restore operation (dumpToolPath in BackupConfig) is not saved between sessions. Every time the user opens the backup/restore dialog, they are prompted to manually re-enter or re-select the path to tools like mysqldump, pg_dump, etc.

The path is preserved within a session (the set config setter in BaseCommandClient.ts retains dumpToolPath when resetting other fields), but it is never written to disk — no user.config.ini key, no localStorage, no electron-store entry.

To Reproduce

1. Open backup or restore for a MariaDB or PostgreSQL connection
2. Set the binary path (e.g. /usr/bin/pg_dump)
3. Complete the operation
4. Close and reopen the app
5. Open backup/restore again — path is blank

Expected behavior The last-used binary tool path should be remembered between sessions, either per-connection or globally as a default.

Possible fix Persist dumpToolPath to user.config.ini (e.g. under [backup]) or store it per-connection in the app's SQLite database.

Version Information

• Reported on commercial edition
• Database types: MariaDB, PostgreSQL

Additional context Reported via support by a commercial user. No existing workaround.