Community SSH node

## Summary

Community SSH nodes (e.g. `node-red-contrib-ssh`, `node-red-node-ssh2`) suffer from timeout issues that cause Node-RED instance reboots. A customer running FlowFuse at high transaction volume (10,000 tx/sec) reported this in October 2025 as a production problem blocking their network automation use case.

## Problem

Existing community SSH nodes:
- Have timeout issues that cause Node-RED instances to crash and reboot unexpectedly
- Are not maintained to enterprise reliability standards
- Have no official FlowFuse support or SLA

## Customer Context

[customer] (https://app-eu1.hubspot.com/contacts/26586079/record/0-2/11137477601) uses FlowFuse for network monitoring automation — integrating monitoring systems with ticketing, automating network equipment tasks via SSH, and connecting to infrastructure APIs. The SSH timeout issue directly impacts their production flows.

## Proposed Solution

## Related

No repository files, tests, or implementation entry points are identified. Start by reviewing the named community SSH nodes and the reported production scenario, then clarify the proposed FlowFuse-supported capability, reliability requirements, and acceptance criteria before implementation.

Written by the indexing model from the issue text.