feat(not-found): add click-to-copy functionality to 404 terminal

[imposterbharathkumarburugu15-cpu]

Description

Fixes #1798

This PR adds click-to-copy functionality to the custom 404 terminal page, making the terminal block interactive and allowing users to easily copy the displayed terminal output.

Changes Made

• Added clipboard copy support using navigator.clipboard.writeText()
• Added success notification using the existing Sonner toast system
• Added error handling for clipboard failures
• Added hover and pointer states to indicate clickability
• Added a "Click to copy" indicator in the terminal header
• Preserved the existing UI and terminal aesthetics

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Checklist

• I have read the CONTRIBUTING.md file
• I have tested these changes locally
• I have run formatting and build checks
• My commit follows the Conventional Commits format
• This change does not introduce breaking changes
• The UI remains consistent with the existing design system

Visual Preview

Before

Users had to manually highlight and copy terminal content.

After

Users can click anywhere on the terminal block to instantly copy the terminal output and receive visual feedback through a toast notification.

Screenshots

[vercel]

@imposterbharathkumarburugu15-cpu is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Hey @imposterbharathkumarburugu15-cpu, welcome to CommitPulse! 🎉

Thanks for opening your first pull request — this is a big deal and we appreciate the effort!

While you wait for a review, please double-check:

• ✅ You've read the CONTRIBUTING.md checklist
• ✅ npm run lint, npm run format, and npm run test all pass locally
• ✅ Your PR has a visual preview if it touches any SVG output
• 💬 You've joined our Discord for faster PR feedback

A maintainer will review your PR shortly. Hang tight! 🚀

[github-actions]

👋 Hey @imposterbharathkumarburugu15-cpu, it looks like you didn't use our PR template!

The section ## Description is missing from your PR description.

Please update your PR description to include all required sections so we can review this properly:

• ## Description — What does this PR do? Which issue does it fix?
• ## Pillar — Which contribution pillar does this fall under?
• ## Checklist — Have you ticked off the quality checklist?

You can find the full template in CONTRIBUTING.md. Just edit your PR description and the needs-details label will be removed automatically. 🙌

[github-actions]

🚨 Hey @imposterbharathkumarburugu15-cpu, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪