feat(web): add VideoHero component

[Kneesal]

Background

The CMS will expose VideoHero content via schema (see feat(cms) schema issue). The web app needs a VideoHero component that consumes this data and renders the hero with video, optional heading/copy, and CTAs.

Expected outcome

• A VideoHero component exists in apps/web that reads VideoHero block data (from Strapi/GraphQL) and renders the hero (video, heading, subheading, optional CTA).
• Component is integrated into the page/dynamic zone rendering pipeline.

Acceptance criteria

• VideoHero component implemented and wired to GraphQL/API response shape.
• Handles video asset (and optional fallback/placeholder).
• Accessible and responsive; optional blur hash or placeholder while loading.
• Integrated where section/components are rendered (e.g. dynamic zone or layout).

Possible solution(s)

1. Add apps/web/src/components/sections/VideoHero.tsx (or under existing structure); consume component fragment from generated client.
2. Reuse shared Media or Hero primitives if they exist; keep styling consistent with design system.

References

• Resolves/Implements schema: feat(cms): add schema for VideoHero component #142 (feat(cms): add schema for VideoHero component)

• apps/web component structure

• packages/graphql generated types

• Parent: epic(web): Web section components for Experience-driven Easter watch page #176 Epic B (Web)

• Related (CMS schema): feat(cms): add schema for VideoHero component #142