Add Support for Cancellation of Long-Running Queries

The ability to cancel long-running queries is currently missing. Without this functionality, users are forced to open new tabs when executing a long-running query. Additionally, long-running queries can impact database performance, making this an important feature to implement.

Current Behavior:

• Long-running queries cannot be canceled once initiated.

Expected Behavior:

• Provide a way to cancel long-running queries directly from the interface.
• Ensure that users receive immediate feedback when a query is successfully canceled.

Additional Consideration:

• Ensure that closing a collection view automatically cancels any active queries tied to that view. This prevents unnecessary resource consumption on the database and ensures that lingering queries don’t continue to run after the user has navigated away.

Start by locating the query execution entry point and the collection-view lifecycle in the extension; the issue does not name files or tests. Trace how active queries are tracked, then define done as an interface cancellation action with immediate feedback and automatic cancellation when its collection view closes.