feat: pre-compile ui and richtext-lexical with react compiler (#7688)

This noticeably improves performance in the admin panel, for example
when there are multiple richtext editors on one page (& likely
performance in other areas too, though I mainly tested rich text).

The babel plugin currently only optimizes files with a 'use client'
directive at the top - thus we have to make sure to add use client
wherever possible, even if it's imported by a parent client component.

There's one single component that broke when it was compiled using the
React compiler (it stopped being reactive and failed one of our admin
e2e tests):
150808f608
opting out of it completely fixed that issue

Fixes https://github.com/payloadcms/payload/issues/7366

test/dev.ts

@@ -7,10 +7,16 @@ import { fileURLToPath } from 'node:url'
 import open from 'open'
 import { loadEnv } from 'payload/node'
 
-import { getNextJSRootDir } from './helpers/getNextJSRootDir.js'
+import { getNextRootDir } from './helpers/getNextRootDir.js'
 import { runInit } from './runInit.js'
 import { createTestHooks } from './testHooks.js'
 
+const prod = process.argv.includes('--prod')
+process.argv = process.argv.filter((arg) => arg !== '--prod')
+if (prod) {
+  process.env.PAYLOAD_TEST_PROD = 'true'
+}
+
 loadEnv()
 
 const filename = fileURLToPath(import.meta.url)
@@ -35,7 +41,7 @@ if (args.turbo === true) {
 const { beforeTest } = await createTestHooks(testSuiteArg)
 await beforeTest()
 
-const { rootDir, adminRoute } = getNextJSRootDir(testSuiteArg)
+const { rootDir, adminRoute } = getNextRootDir(testSuiteArg)
 
 await runInit(testSuiteArg, true)