feat: enhance interrupt handling and container resource configuration

- Introduced a shared interrupt signaling mechanism to allow tools to check for user interrupts during long-running operations.
- Updated the AIAgent to handle interrupts more effectively, ensuring in-progress tool calls are canceled and multiple interrupt messages are combined into one prompt.
- Enhanced the CLI configuration to include container resource limits (CPU, memory, disk) and persistence options for Docker, Singularity, and Modal environments.
- Improved documentation to clarify interrupt behaviors and container resource settings, providing users with better guidance on configuration and usage.

cli-config.yaml.example

@@ -90,6 +90,14 @@ terminal:
 #   timeout: 180
 #   lifetime_seconds: 300
 #   modal_image: "nikolaik/python-nodejs:python3.11-nodejs20"
+#
+# --- Container resource limits (docker, singularity, modal -- ignored for local/ssh) ---
+# These settings apply to all container backends. They control the resources
+# allocated to the sandbox and whether its filesystem persists across sessions.
+#   container_cpu: 1              # CPU cores (default: 1)
+#   container_memory: 5120        # Memory in MB (default: 5120 = 5GB)
+#   container_disk: 51200         # Disk in MB (default: 51200 = 50GB)
+#   container_persistent: true    # Persist filesystem across sessions (default: true)
 
 # -----------------------------------------------------------------------------
 # SUDO SUPPORT (works with ALL backends above)