[Feature Request]: Add SSH Keepalive / Heartbeat option to prevent idle connection timeouts

Problem description
When connecting to a Redis database through an SSH tunnel in RedisInsight, the connection frequently drops after a period of inactivity. Returning to perform operations after being idle results in connection broken errors, requiring manual reconnection.

Adding an SSH Keepalive / Heartbeat setting (or automatic background ping for SSH tunnels) would keep the underlying connection alive during long idle periods and deliver a seamless experience.

How often do you encounter this problem
Every time the connection is left idle for more than a few minutes (e.g., 5–15 minutes, depending on network or server timeout policies).

Alternatives considered

• Manually adjusting ClientAliveInterval and ClientAliveCountMax on the SSH server (often restricted due to lack of admin permissions).
• Setting up a local SSH tunnel in the terminal with -o ServerAliveInterval=30 and directing RedisInsight to connect via localhost (requires extra manual steps outside the app).

Additional information
Adding a simple configurable "SSH Keepalive Interval (seconds)" field under the SSH Tunnel settings (or enabling background heartbeats by default) would easily solve this issue for users operating behind strict firewalls or NATs.

Start by locating the existing SSH Tunnel settings and the connection-handling entry point in RedisInsight. Review how tunnel options are represented and applied, then determine the scope for a configurable keepalive interval or background heartbeat. Done means the setting is available under SSH Tunnel configuration and idle tunneled connections remain usable.