chore(deps): upgrade to React 19

[drichar]

Description

This PR upgrades the React dependencies to version 19 across all packages and applies the official React 19 codemods to ensure compatibility with the new version.

Details

• Upgrade core React dependencies:
  • react and react-dom to 19.0.0
  • @types/react and @types/react-dom to 19.0.0
  • Update peer dependency ranges to include ^19.0.0
• Upgrade supporting libraries for React 19 compatibility:
  • @testing-library/react to 16.1.0
  • TanStack store packages to 0.7.0
• Apply official React 19 codemods:
  • remove-context-provider: Simplify Context.Provider syntax
  • use-context-hook: Migrate from useContext to use hook
  • scoped-jsx: Update JSX namespace imports

[drichar]

One of the breaking changes in v19 is the ReactNode type. As a result, the WalletProvider exported by use-wallet-react built with React v19 cannot accept an explicitly typed children prop from a React v18 (or lower) project.

A common pattern in Next.js App Router projects is a client component containing all of the root context providers, like the one in our Next.js example app:

use-wallet/examples/nextjs/src/app/providers.tsx

Lines 32 to 34 in 97fbae0

	export function Providers({ children }: { children: React.ReactNode }) {
	return <WalletProvider manager={walletManager}>{children}</WalletProvider>
	}

The resulting error can be seen in this CI run: https://github.com/TxnLab/use-wallet/actions/runs/12699514184/job/35400307744?pr=332

If children is implicitly typed, there's no error. But there are bound to be other Next.js projects that follow the providers pattern, and other situations where explicit types are used. I'll need to determine a workaround or wait until React v19 is more widely adopted before moving forward with this upgrade.