Fix for issue where retries continue on a closed runtime

[tofarr]

End-user friendly description of the problem this fixes or functionality that this introduces

This PR fixes an issue where retry attempts would continue even after a runtime was closed, which could lead to unnecessary resource usage and potential errors.

Give a summary of what the PR does, explaining any non-trivial design decisions

The PR makes the following changes:

1. Adds a _stop_if_closed method to the RemoteRuntime class that checks if the runtime is closed
2. Integrates this check into the retry logic for both _wait_until_alive and _send_action_server_request methods
3. Improves error logging in the standalone conversation manager by adding stack traces for better debugging

Key changes:

• Added self._stop_if_closed to the stop conditions in retry decorators
• Enhanced error logging in _cleanup_stale method to include stack traces

This change ensures that retry attempts are properly terminated when a runtime is closed, preventing unnecessary resource usage and potential errors from retrying operations on a closed runtime.

Link of any specific issues this addresses

N/A

---

To run this PR locally, use the following command:

docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:aa87fe2-nikolaik   --name openhands-app-aa87fe2   docker.all-hands.dev/all-hands-ai/openhands:aa87fe2

[xingyaoww]

This LGTM and I just pushed a commit that add remote_runtime_enable_retries to all eval scripts