Architecture: Docker-based tool sessions

[scttfrdmn]

HubZero supports interactive computational tool sessions. The current deployment runs tools directly on the EC2 host, which limits isolation and scalability.

Proposed changes:

• Define a container-based tool session architecture (likely ECS or standalone Docker on EC2)
• Each tool session runs in an isolated container with resource limits
• Session lifecycle management (start, stop, timeout)
• Networking: tool sessions need access to HubZero application and potentially external resources
• Implement session storage/state persistence

Open questions:

• ECS Fargate vs. Docker-on-EC2 for tool sessions
• Session timeout and cleanup strategy
• Network isolation requirements per tool type