[Bug] Issue with Code Runner Extension When Terminal is Already Running a Process

Subject: Issue with Code Runner Extension When Terminal is Already Running a Process

**Description:**

I am encountering an issue with the Code Runner extension in Visual Studio Code when I have a terminal open that is already running a process. When I open a different file and click on the "Run" button, the extension attempts to execute the command in the existing terminal, which is reserved for the previous process. Ideally, it should open a new instance or tab of the terminal to run the new command.

**Steps to Reproduce:**

1. Open a terminal in VS Code.
2. Start a long-running process or server in the terminal, so it remains active.
3. Open a different file in VS Code.
4. Click on the "Run" button for the code in the new file.

**Expected Behavior:**

I expected the Code Runner extension to open a new terminal instance or tab to run the command from the new file, even when a terminal with a running process is already open. This behavior would prevent conflicts with the existing terminal.

**Actual Behavior:**

The Code Runner extension attempts to execute the command in the existing terminal, which is already reserved for the previous process. This can cause confusion and conflicts.

**Environment:**

- Visual Studio Code Version: 1.82.2
- Code Runner Extension Version: [0.12.0]
- Operating System: [Debian 13 Linux]

demo video
[screen-record-bug.webm](https://github.com/formulahendry/vscode-code-runner/assets/91236511/eaea090f-7886-41e1-aeff-dfe3e0b8b3f7)