chore(test): Disable Vitest globals

[timfish]

• Ref Migrate from jest to vitest and stop using jsdom based tests #11084

We should not use Vitest globals except where they are required.

This PR:

• Disables globals in our root vite.config.ts
• Fixes missing imports
• Sets globals: true for React since there are load of test failures without it and I couldn't immedialy work out why

[AbhiPrasad]

let's make the vitest import the first import on the file

[timfish]

Oh, I thought linting would sort this all out!

[timfish]

Ah, this is because since Biome was added, import order has not been enforced. I looked to get this working again and it impacts hundreds of files

[codecov]

❌ 196 Tests Failed:

Tests completed	Failed	Passed	Skipped
4650	196	4454	323

View the top 3 failed test(s) by shortest run time

suites/breadcrumbs/process-thread/test.ts > suites/breadcrumbs/process-thread/test.ts

Stack Traces | 0s run time

ReferenceError: describe is not defined
 ❯ Module.conditionalTest utils/index.ts:43:7
 ❯ .../breadcrumbs/process-thread/test.ts:38:1

suites/child-process/test.ts > suites/child-process/test.ts

Stack Traces | 0s run time

ReferenceError: describe is not defined
 ❯ Module.conditionalTest utils/index.ts:43:7
 ❯ suites/child-process/test.ts:47:3

suites/contextLines/memory-leak/test.ts > suites/contextLines/memory-leak/test.ts

Stack Traces | 0s run time

ReferenceError: describe is not defined
 ❯ .../contextLines/memory-leak/test.ts:3:1

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}