fix:add error page for incorrect ipfs:// usage with domain names

[SAHU-01]

Description

This PR fixes #1316, by adding an educational error page that appears when users incorrectly use ipfs:// protocol with domain names instead of ipns://.

Problem

Users often confuse ipfs:// and ipns:// protocols, using ipfs://example.com when they should use ipns://example.com. This creates confusion and perpetuates incorrect URIs in documentation and blog posts.

Solution

• Added detection for domain names used with ipfs:// protocol
• Created an educational error page explaining the difference
• Styled to match IPFS WebUI design system
• Provides "Continue to ipns://..." button for seamless redirection

Testing

Tested on Chromium with the following URLs:

• ipfs://example.com → Shows error page → Redirects to ipns://example.com
• ipfs://docs.ipfs.tech → Shows error page → Redirects to ipns://docs.ipfs.tech
• ipfs://ipfs.io → Shows error page → Redirects to ipns://ipfs.io
• ipfs://QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco → Works normally (valid CID)

Screenshots

Screen.Recording.2025-09-21.at.11.50.55.PM.mov

Considerations:

• The 500 error for example.com is expected as it doesn't have DNSLink records
• The regex error in console doesn't affect functionality, it's a Chromium limitation with complex redirect rules
• I tried matching the theme of exsisting pages, still changes could be made here to match the overall UI

Reviewers: @lidel