Vitest vscode plugin is listening on the port which is needed by vite

[fourdim]

Describe the bug

Possibly related to #443.

Reproduction

1. Download the repo.

git clone https://github.com/toeverything/blocksuite

2. Install Vitest VSCode plugin.

3. Install dependencies.

yarn

4. Development mode.

yarn dev

Here Vite is not binding to the default 5173 but 5175.

Output

[INFO 4:53:41 PM] [v1.6.0] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 4:53:41 PM] [API] Running Vitest v2.1.2 (blocksuite/vitest.workspace.js) with Node.js@v20.17.0: /home/fourdim/.config/nvm/versions/node/v20.17.0/bin/node 
[INFO 4:53:42 PM] [Worker] �[33mThe CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.�[39m
[INFO 4:53:42 PM] [Worker] Forced re-optimization of dependencies
[INFO 4:53:42 PM] [Worker] Port 5173 is in use, trying another one...
[INFO 4:53:42 PM] [API] Vitest v2.1.2 (blocksuite/vitest.workspace.js) child process 78366 created
[INFO 4:53:42 PM] [VSCODE] Watching blocksuite with pattern **/*

Version

v1.6.0

Validations

• Check that you are using the latest version of the extension
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.