feat(website): highlight KEDA autoscaling and deployment docs

[Wassim Chegham (manekinekko)]

Summary

• Give the Kubernetes section a light surface with official full-color Kubernetes and KEDA artwork.
• Lead with KEDA autoscaling and use three borderless feature tiles with aligned graphics, headings, and descriptions that stack on mobile.
• Link the scaling headline to Scope's autoscaling guide, preserve the KEDA project link, and add Kubernetes deployment under the footer's Learn group.
• Document the layout and artwork provenance and add responsive layout, navigation, and accessibility regression coverage.

Demos

Website-only UX change. The current screenshot is attached below; video recordings are not attached.

Before

The original blue Kubernetes section and Learn footer. Video not attached.

After

Light background, official KEDA wordmark, aligned feature tiles, and a linked Scope autoscaling headline.

Testing

Run from website/ with the site's pinned pnpm and a compatible Node version:

• volta run --node 22.22.0 npx --yes pnpm@10.29.1 test — passed, 7 plugin regression tests.
• volta run --node 22.22.0 npx --yes pnpm@10.29.1 test:a11y --grep 'landing page and interactive example are accessible|infrastructure feature tiles|privacy links and landmarks' — passed, 24 browser tests covering light/dark themes and 1280px/320px widths. This command also successfully builds the production site with SITE=https://microsoft.github.io BASE_PATH=/scope.
• Manual local-preview review confirmed the feature order, aligned text, KEDA copy, autoscaling destination, and the Learn footer deployment link. The deployment guide returned HTTP 200.
• Both vendored SVGs were compared against their official CNCF sources and match.

Root application suites were not run; this change is confined to the standalone website package.

Documentation and compatibility

Updated website/README.md with layout, branding, artwork provenance, and navigation details.

Breaking changes, API/CLI compatibility impacts, and upgrade steps: None.

Checklist

• If Portal features changed, keep CLI capabilities in sync. (N/A: website-only change.)
• If Portal components changed, update their Storybook stories. (N/A: no Portal components changed.)
• If database changes require a migration, include up() / down() and keep it CosmosDB-compatible. (N/A: no database changes.)
• If dependencies changed, update the lockfile and regenerate NOTICE / NOTICE-REVIEW.txt with pnpm notice as needed. (N/A: no dependency changes.)
• Video showing the behavior before the suggested change
• Video showing the behavior after the suggested change