Frontend updated for v1.1.0 — version badges, VS Code extension visibility

[mesrikanthreddy]

Summary

Tracking issue for visibility on a frontend update shipped in PR #32 (`dev` → `master`), so the change is discoverable outside the PR history.

What was fixed

The landing page and dashboard sidebar were still showing stale v1.0.0 branding after the v1.1.0 release, and the VS Code extension (shipped this release) wasn't mentioned anywhere on the site:

• Version badges bumped `v1.0.0` → `v1.1.0` (`Landing.tsx` nav badge, `Sidebar.tsx` dashboard badge)
• Fixed Homebrew install command casing: `brew install YTT-Global/tap/kshield` → `brew install ytt-global/tap/kshield` (the actual tap name is lowercase)
• Added "VS Code extension with inline diagnostics" to the feature list
• Added a 5th install tab: `code --install-extension YTTGlobal.kshield-vscode`
• Made the install-tab row horizontally scrollable so the extra tab doesn't clip on narrow screens

Verification

• `tsc --noEmit` clean
• Production build (`GITHUB_PAGES=true npm run build`) succeeds
• Dev server serves without errors
• Not visually screenshotted — no headless browser available in the environment this was built in; source strings and build output were verified directly instead

Follow-up (not done, out of scope for this pass)

`frontend/package.json`'s own `"version": "1.0.0"` (npm metadata, not user-visible) is also stale relative to the 1.1.0 release — left untouched, flagging here in case it should be bumped too.

Links

• PR: release: sync master with v1.1.0 frontend updates #32