Is your feature request related to a problem? Please describe.
When using HeidiSQL with MSSQL or PostgreSQL, database connections may drop after a period of inactivity, network timeouts, or temporary connectivity issues. When this happens, the connection remains in a disconnected state and any attempt to browse tables or switch schemas results in errors, requiring a manual reconnect.
In contrast, MySQL connections in HeidiSQL automatically recover by reconnecting when user interaction occurs, which provides a smoother workflow.

Describe the solution you'd like
Implement automatic connection recovery for MSSQL and PostgreSQL similar to the existing behavior for MySQL. If a connection has been dropped, HeidiSQL should transparently attempt to reconnect when the user performs an action such as switching tables, schemas, or refreshing the object browser.

Describe alternatives you've considered
The only current workaround is manually reconnecting after an error occurs. This interrupts the workflow and creates an inconsistent user experience compared to MySQL connections.

Additional context
This feature would significantly improve usability for long-running HeidiSQL sessions and environments with idle timeouts. Aligning MSSQL and PostgreSQL connection behavior with MySQL would also provide a more consistent experience across supported database engines.