feat: add Next.js SSR compatibility support

[lucky7323]

Problem

BridgeWise SDK React components and hooks cause runtime errors and hydration mismatches when used in Next.js SSR environments due to direct access to browser APIs (window, document, localStorage) during server-side rendering.

Solution

This PR introduces comprehensive SSR compatibility for BridgeWise components while maintaining backward compatibility with existing client-side usage.

Key Features

🛠️ SSR-Safe Utilities

• isServer/isClient environment detection
• safeStorage API with fallback support for localStorage operations
• createBrowserGuard for explicit server access error handling

⚛️ React SSR Hooks

• useIsClient - prevents hydration mismatches by detecting client-side hydration completion
• useIsomorphicLayoutEffect - eliminates SSR warnings from useLayoutEffect

🧩 SSR Components

• ClientOnly component with fallback support for server-side rendering
• All existing components remain unchanged but gain SSR safety

📦 Next.js Adapter Package

• @bridgewise/next-adapter - dedicated package with next/dynamic wrappers
• Drop-in replacements: BridgeStatusDynamic, BridgeCompareDynamic, ClientOnlyDynamic
• Zero configuration required for Next.js App Router and Pages Router

Usage Examples

Basic SSR-safe usage:

import { BridgeStatus, ClientOnly } from '@bridgewise/ui-components';

export default function BridgePage() {
  return (
    <ClientOnly fallback={<div>Loading...</div>}>
      <BridgeStatus chainId={1} />
    </ClientOnly>
  );
}

Next.js dynamic imports:

import { BridgeStatusDynamic } from '@bridgewise/next-adapter';

export default function BridgePage() {
  return <BridgeStatusDynamic chainId={1} />;
}

Compatibility

• ✅ Next.js 13.4+ (App Router and Pages Router)
• ✅ React 18+ and React 19
• ✅ Zero breaking changes to existing client-side usage
• ✅ TypeScript fully supported
• ✅ 'use client' directives preserved for React 18+ compatibility

Technical Implementation

• Framework-agnostic core utilities in existing @bridgewise/ui-components
• Separate Next.js-specific adapters to maintain framework neutrality
• Proper error boundaries for server-side browser API access
• Consistent hydration behavior across all components

This implementation ensures BridgeWise components work seamlessly in modern SSR frameworks while preserving full backward compatibility.

Fixes #58