Add retry mechanism with exponential backoff for Docker availability check

[mrrobot47]

Problem

Under heavy system load, docker ps can occasionally return exit code 1 due to transient Docker daemon/socket unresponsiveness, even when Docker is properly installed and running. This causes EasyEngine to fail with "Docker not installed or not running" error unnecessarily.

Solution

• Added retry mechanism with exponential backoff (1s → 2s → 4s, total 7s max wait) for the Docker availability check
• Moved debug logging (argv, config paths) to the start of Runner::start() for better debugging visibility when Docker checks fail
• Added debug logging for retry attempts to help diagnose transient failures

[Copilot]

Pull request overview

This PR adds resilience to the Docker availability check by implementing a retry mechanism with exponential backoff to handle transient Docker daemon failures under heavy system load. It also improves debugging by moving debug logging statements earlier in the execution flow.

Key changes:

• Implemented retry logic with exponential backoff for the docker ps command to handle transient Docker daemon unresponsiveness
• Relocated debug logging statements to the beginning of Runner::start() for better visibility when Docker checks fail

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.