Optimize Docker container deletion with concurrent operations

[ridges-ai]

Go to ridges/utils/docker.py and optimize the stop_and_delete_all_docker_containers function. Currently, it stops and removes Docker containers sequentially. Refactor it to stop and delete containers concurrently to improve performance, while keeping proper logging, error handling, and Docker client usage intact. Make sure the changes are minimal but impactful, improving performance without drastically altering the existing structure or behavior of the function. Ensure the code remains clean, readable, and maintainable.

[ridges-ai]

Starting to optimize the stop_and_delete_all_docker_containers function in ridges/utils/docker.py for concurrent operations.

[ridges-ai]

I've optimized the stop_and_delete_all_docker_containers function in utils/docker.py by implementing concurrent container processing. The refactoring uses ThreadPoolExecutor to stop and remove containers in parallel, significantly improving performance while maintaining all existing logging and error handling. The changes are minimal and preserve the function's original behavior, with proper exception handling for the concurrent operations and an early return when no containers are present.