Add homepage patch support notice

[Lucas-FManager]

Problem

The homepage does not currently surface OKD patch support guidance, so users have to infer update behavior from release/update docs.

Root cause

The site has release notes and update docs, but no prominent homepage notice that explains how OKD patch releases are consumed.

Approach

• Added a homepage PatchSupportNotice immediately below the hero.
• Kept it as a full-width Docusaurus section using existing theme tokens.
• Linked the call to action to the official OKD update guidance.
• Wording stays conservative: OKD publishes community patch releases through the stable update channel after verification passes, and users should use the update graph/latest stable release instead of assuming every patch number exists.

Security review

This is a content-only homepage change. It does not add scripts, dependencies, credentials, tracking, or runtime data access. The only added outbound link points to official OKD documentation.

Verification

• npm ci -> success; existing audit/deprecation warnings remain in the lockfile dependency tree
• npm run build -> success; existing Docusaurus/Sass warnings remain
• git diff --check -> passed, with Windows line-ending warnings only

Note: npm run typecheck currently fails on pre-existing Cannot find namespace 'JSX' errors across existing components (HomepageFeatures, HomepageHero, HomepageInsideOKD, HomepageSoWhatIsOKD, OKDLogo, and src/pages/index.tsx). This PR does not introduce that repo-wide TypeScript config issue.

Fixes #113