test timeout overwrite also applied when debugging

Describe the bug

When needing to override the timeout for a test because the test takes more than the default 5000ms to run, the override value is then also taken into account while debugging

This shouldn't be, because then, when debugging, the test will likely fail during debugging when hitting a breakpoint

See prior discussion: https://github.com/vitest-dev/vscode/discussions/539

Reproduction

System Info

-

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• 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.

Start by reviewing how test timeout overrides are applied during normal runs and how the debugging path invokes them, then compare the behavior with the prior discussion at vitest-dev/vscode#539. Done means an overridden timeout still works for regular test execution but does not shorten or constrain a test while debugging.