fix: prevent AbortSignal listener memory leak

- Add abort listener cleanup in Query.close() to prevent memory leak
- Add abort listener cleanup in ControlDispatcher.shutdown()
- Remove AbortController recreation in Session.handleInterrupt()

This fixes the MaxListenersExceededWarning that occurred when:
- Creating 11+ Query instances in SDK/non-interactive mode
- Multiple user interrupts (Ctrl+C) in interactive mode
- Intensive control request scenarios

packages/cli/src/nonInteractive/session.ts

@@ -408,7 +408,8 @@ class Session {
   private handleInterrupt(): void {
     debugLogger.info('[Session] Interrupt requested');
     this.abortController.abort();
-    this.abortController = new AbortController();
+    // Do not create a new AbortController to prevent listener leaks.
+    // Subsequent queries will check signal.aborted and fail immediately.
   }
 
   private setupSignalHandlers(): void {