feat: add react-compiler export condition

[stipsan]

The React Compiler were struggling to understand the flow of <PortableText>:

react-portabletext/src/react-portable-text.tsx

Lines 42 to 67 in 11fbc8a

	export function PortableText<B extends TypedObject = PortableTextBlock>({
	value: input,
	components: componentOverrides,
	listNestingMode,
	onMissingComponent: missingComponentHandler = printWarning,
	}: PortableTextProps<B>): JSX.Element {
	const handleMissingComponent = missingComponentHandler || noop
	const blocks = Array.isArray(input) ? input : [input]
	const nested = nestLists(blocks, listNestingMode || LIST_NEST_MODE_HTML)
	const components = useMemo(() => {
	return componentOverrides
	? mergeComponents(defaultComponents, componentOverrides)
	: defaultComponents
	}, [componentOverrides])
	const renderNode = useMemo(
	() => getNodeRenderer(components, handleMissingComponent),
	[components, handleMissingComponent],
	)
	const rendered = nested.map((node, index) =>
	renderNode({node: node, index, isInline: false, renderNode}),
	)
	return <>{rendered}</>
	}

And it got different results for its useMemo deps arrays that were used to memo renderNode, and thus opted out from optimizing it.

Here's a diff of what happens if you add react-compiler without refactoring anything, and with the changes in this PR: https://npmdiff.dev/%40portabletext%2Freact/3.0.18-canary.0/3.1.0-canary.2/package/dist/index.compiled.js/

What I like about the implementation on main is that if the components and onMissingComponent props were stable, then a changing value prop didn't result in getNodeRenderer and mergeComponents being called more than once. I wanted to preserve this behaviour, while also changing the code so that the compiler understands it and can auto memoize it further.

By splitting the work into two separate components we preserve the previous memoization, while adding a few new benefits:

• Since <PortableText> is now wrapped in memo it can opt-out of looping a possibly very deep recursive tree of renderNode if parent components rerender but the props given to <PortableText> haven't changed.
• It's easier to track why portable text components rerender, as react profiling will tell you that "PortableTextRenderer rerendered because prop 'renderNode' changed" instead of "PortableText rerendered because hook 2 changed"