Fix TypeScript import errors in RSCRoute and RSCProvider

Changed from `import ReactClient from 'react/index.js'` to the
simpler and more compatible `import * as React from 'react'`.

The 'react/index.js' path caused module resolution issues in Jest
and TypeScript errors without esModuleInterop. The simpler import
works correctly in all environments.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: justin808

packages/react-on-rails-pro/src/RSCProvider.tsx

@@ -13,12 +13,10 @@
  */
 
 import type { ReactNode } from 'react';
-import ReactClient from 'react/index.js';
+import * as React from 'react';
 import type { ClientGetReactServerComponentProps } from './getReactServerComponent.client.ts';
 import { createRSCPayloadKey } from './utils.ts';
 
-const React = ReactClient;
-
 type RSCContextType = {
   getComponent: (componentName: string, componentProps: unknown) => Promise<ReactNode>;
 

packages/react-on-rails-pro/src/RSCRoute.tsx

@@ -15,12 +15,10 @@
 /// <reference types="react/experimental" />
 
 import type { ReactNode } from 'react';
-import ReactClient from 'react/index.js';
+import * as React from 'react';
 import { useRSC } from './RSCProvider.tsx';
 import { ServerComponentFetchError } from './ServerComponentFetchError.ts';
 
-const React = ReactClient;
-
 /**
  * Error boundary component for RSCRoute that adds server component name and props to the error
  * So, the parent ErrorBoundary can refetch the server component