fix: correct the driver matrix against netOrk v0.28.0

Audited the drivers that actually ship in v0.28.0 (vendor-drivers.txt at the
tag, each driver package at its pin) instead of carrying the old table on.

- Reboot: netOrk's reboot really restarts only OpenWrt and Proxmox. For every
  other driver the request reported success while nothing happened, so the
  column now says so. Rebooting through an update run is mentioned in a note.
- Config push: OPNsense, ProCurve, TP-Link JetStream, Netgear Smart and Proxmox
  do get configuration written by netOrk; the column was missing them.
- Zyxel is a VMG residential gateway, not a switch: no LLDP, VLANs or health,
  but SSIDs. Fritz!Box is read-only and has no health metrics. Proxmox has no
  Docker view.
- netgear is two drivers, netgear_smart and netgear_plus. New: hpe_officeconnect,
  qnap_qts, yealink.
- The built-in NAPALM drivers are installed but untested with netOrk and get
  none of its driver-specific features; the page no longer says "supported".
- Notes explain the Health, LLDP, Config push and Reboot columns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/pages/Home.tsx

@@ -10,9 +10,9 @@ import { useLang } from '../context/LangContext'
 import { linkify } from '../lib/glossary'
 
 const DRIVERS = [
-  'Arista EOS', 'Cisco IOS', 'Cisco IOS-XE', 'Cisco NX-OS', 'Fritz!Box',
-  'HP ProCurve / Aruba', 'Juniper JunOS', 'Linux', 'Netgear', 'OpenMediaVault',
-  'OpenWRT', 'OPNsense', 'Proxmox VE', 'Sonos', 'TP-Link Jetstream', 'Zyxel',
+  'Fritz!Box', 'HPE OfficeConnect', 'HPE ProCurve / Aruba', 'Linux', 'Netgear',
+  'OpenMediaVault', 'OpenWrt', 'OPNsense', 'Proxmox VE', 'QNAP QTS', 'Sonos',
+  'TP-Link JetStream', 'Yealink', 'Zyxel VMG',
 ]
 
 function BrowserFrame({ label, children }: { label: string; children: React.ReactNode }) {