fix: interpret only mode

[patak-dev]

It wasn't working when only was applied to a task. Seems to be working fine now (also corrected a typo)

[antfu]

I was thinking the .only on task should affect the scope of the current suite. Is this the behaviour of Jest or others? (I haven't use them before)

[patak-dev]

You are right, looks like test.only is scoped to the file https://jestjs.io/docs/api#testonlyname-fn-timeout. Probably better to scope to the suite level in vitest. Closing this one.