feat: add Legal Links section to footer

[yachikadev]

What does this PR do?

Adds a new Legal Links section to the site footer as requested in the issue.
The new column includes Privacy Policy, Guidelines, and Documentation links —
making important resources easily accessible to users and contributors.

Changes Made

• Added LEGAL_LINKS array in src/components/Footer.tsx with three links:
  • Privacy Policy → /privacy-policy
  • Guidelines → Code of Conduct on GitHub
  • Documentation → Development guide on GitHub
• Added a new Legal Links column in the footer grid
• Updated grid layout to lg:grid-cols-5 to accommodate the new column
• Reused existing FooterLink component so styling, hover effects, and
  typography are fully consistent with the rest of the footer

Why this matters

Missing legal links reduce trust and discoverability for first-time users
and open-source contributors. Footer is the standard and most accessible
placement for policy-related links.

Closes #1323

[github-actions]

GSSoC Label Checklist 🏷️

@Umbrella-io — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[yachikadev]

Hey! Really sorry for the late PR — my git got stuck while syncing
the branch with remote and it took some time to resolve. Everything
is working fine now. Thanks for your patience!

Could you please add the quality label and other relevant labels
to this PR as they help with GSSoC points!

Also wanted to mention that the visual regression check failure is
not caused by my changes — it was already failing before my PR.

[Priyanshu-byte-coder]

CI is failing on this PR. Please fix the TypeScript/test errors before we can merge. Run npm run typecheck and npm test locally to reproduce.

[vercel]

@yachikadev is attempting to deploy a commit to the legitox's projects Team on Vercel.

A member of the Team first needs to authorize it.

[yachikadev]

Hi! I wanted to explain the situation — my git was stuck and I was
unable to push my changes on time, which caused a 6 hour delay in
submitting this PR. By the time I pushed, someone else had already
submitted a PR for the same issue and it got merged into main.

Due to that merge, my PR is now showing a CI failure because of a
duplicate LEGAL_LINKS declaration conflict — which is not a code
error on my part, but a result of the same feature already being
in main.

Could you please consider giving me credit for this issue since I
had worked on it independently and the only reason for the late
submission was a git issue on my end?

[Priyanshu-byte-coder]

New UI/feature PRs are on hold during the code quality sprint — see discussion #2651. PRs for tests, refactoring, bug fixes, docs, and performance are welcome.

[Priyanshu-byte-coder]

New feature/UI PRs are on hold during the code-quality sprint — see discussion #2651. We'll revisit after the sprint; tests, refactors, and bug-fix PRs are the priority right now.

[Priyanshu-byte-coder]

The Legal Links section already landed on main (see Footer.tsx — LEGAL_LINKS exists), and this diff re-declares the same const, which is a compile error. Closing as already implemented.