Implement partnership section components and payment status refetch

[Holytech]

Description

This PR introduces the Call for Partnership section on the landing page, modularized into reusable components, along with typography consistency improvements across page titles and manual payment verification enhancements in the tickets flow.

Key Changes:

• Call for Partnership Section:
  • Created a modular partnership section under app/component/partnership/ (PartnershipHeader, PartnershipBenefits, PartnershipContactCard, PartnershipContactSection, WhatsAppIcon, data.ts, types.ts).
  • Integrated direct partnership contact cards for Abidemi (abidemi@gdgibadan.com) and Josh (josh@gdgibadan.com) with 1-click copy-to-clipboard (with toast feedback) and direct email links.
  • Added dual email CTA button ("Email Partnership Team") and WhatsApp CTA with official WhatsApp icon and #25D366 branding.
  • Integrated CallForPartnership component into the landing page (app/page.tsx).
• Typography & Consistency:
  • Harmonized section titles across the landing page to sentence case with comfortable line-height spacing (CallForSpeakers, SwagsAndTickets, HowItGoesDown, PartnershipHeader, and DevfestHero button labels).
• Payment & Tickets Flow:
  • Added manual payment status refetch / verification functionality in the tickets success workflow (SuccessOrderCard, PaymentSuccess, success/page.tsx).

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Visual and functional testing on desktop and mobile viewports via local development server (yarn dev).
• Verified copy-to-clipboard functionality and mailto links for abidemi@gdgibadan.com and josh@gdgibadan.com.
• Verified WhatsApp CTA link with pre-filled sponsorship message.
• Executed TypeScript type check (npx tsc --noEmit) with 0 errors.
• Executed linter (yarn lint) with 0 warnings or errors.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[netlify]

❌ Deploy Preview for heroic-ganache-f5f2e7 failed.

Name	Link
🔨 Latest commit	e670355
🔍 Latest deploy log	https://app.netlify.com/projects/heroic-ganache-f5f2e7/deploys/6aa3d7c3f588ff00087c7531

[supabase]

This pull request has been ignored for the connected project nxbuklamepmtosouyctf because there are no changes detected in backend/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.