fix(metadata): implement dynamic network url path routing for token page and social previews

[DevRushd]

Summary

Replaces hardcoded NETWORKS.testnet references in three server-side entry points with path-based dynamic network routing. The network context is now carried directly in the URL path: /token/[network]/[contractId].

Changes

Directory Restructure

• Moved frontend/app/token/[contractId] → frontend/app/token/[network]/[contractId]
• Moved frontend/app/api/og/token/[contractId] → frontend/app/api/og/token/[network]/[contractId]
• Moved frontend/app/api/token/[contractId]/metadata → frontend/app/api/token/[network]/[contractId]/metadata

Code Changes

• types/network.ts: Added getNetworkConfig(network: string) helper that maps "mainnet" → NETWORKS.mainnet and falls back to NETWORKS.testnet
• token/[network]/[contractId]/page.tsx: Reads network from URL params, uses getNetworkConfig for validateTokenContract and fetchTokenInfo calls, updates OG image URLs to include network segment
• api/og/token/[network]/[contractId]/route.tsx: Reads network from URL params, constructs network config dynamically
• api/token/[network]/[contractId]/metadata/route.ts: Reads network from URL params, constructs network config dynamically
• PublicTokenPage.tsx: Accepts network prop, syncs URL network with NetworkProvider context, fixes InvalidTokenContract import path

Closes #401

[drips-wave]

@DevRushd Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[zachyo]

Hi @DevRushd , kindly fix conflicts. Thanks

[DevRushd]

Hi @zachyo, I have fully resolved the conflict