fix: prevent hydration errors in header navigation

[Preksha0401]

Problem

The header navigation components were causing SSR hydration errors during production builds.

Errors observed:

• document is not defined
• Hydration mismatch between server and client
• Build failures on pages using header navigation

This happened because browser-only logic (DOM access, hover interactions, animations)
was executed during server-side rendering.

Solution

• Converted header navigation components (Product, Solutions, Docs, Resources)
  to client-only rendering using next/dynamic with ssr: false
• Ensured browser-specific logic runs only on the client
• Prevented server from attempting to render DOM-dependent components

Result

• npm run build completes without SSR/hydration errors
• Header navigation works correctly in the browser
• Production-safe SSR behavior restored

Files Changed

• components/ui/header.tsx
• components/nav/productSection.tsx

Verification

• Local npm run build passes
• No hydration warnings in browser console
• Navigation dropdowns function as expected

Verification Screenshot