Delay system response after using the CSV: feature in DB2 for IBM i queries

I have been noticing a problem not necessarily caused by the DB2 for IBM i extension, where actions like Run SQL Statement command (Ctrl+R) to run the query statement does not seem to be working. I at times think I did not press the key sequence. Many things VS Code slow down also, which is why I don't specifically thinks its just this extension.

There is no indication that anything is happening. Nothing obvious in the VS Code process explorer. Then after around a minute or two the Run SQL Statement will start up. If I think I did not properly press Ctrl+R then I press it again and after a minute or two I get a results tab for each time I pressed Ctrl+R.

If I don't press Ctrl+R to produce a CSV results for a few minutes then the system works as expected but will stop working as described above.

I only noticed this with CSV and not with the results in the output channel. I don't see this with the JSON results output as I don't use that form.

**To Reproduce**

Steps to reproduce the behavior:
1. Build a query
2. Prepend `CSV:` to the statement
3. Press Ctrl+R
4. Close the opened tab when done.
5. Repeat until you notice Ctrl+R does not seem to be doing anything.

**Expected behavior**

VS Code to perform the Run SQL Statement command.
I think

**Screenshots**

Too difficult to capture this in this form.

**Environment**

- OS: Windows 11
- Extension Version 1.14.0

**Additional context**

Start by reproducing the delay using the Run SQL Statement command (Ctrl+R) with a query prefixed by CSV:, repeating the steps until the response is delayed. Compare CSV behavior with the output channel and JSON results, and consider the issue resolved when repeated CSV runs respond promptly without duplicate result tabs.

Written by the indexing model from the issue text.