Decommission the old Plex VM

Plex has run as a container on the Docker host since the 2026-09-16
migration. The old Debian 11 VM (10.100.0.24) is now retired per
plex-docker-migration.md section 9, steps 1, 2 and 4-7:

- removed from the Veeam "Backup VMs" job
- guest shut down gracefully, pre-migration snapshot removed and
  consolidated back to Plex.vmdk
- Guacamole "Plex SSH" connection deleted
- .24 / 10.50.0.31 DHCP leases released on the UDM

The VMDKs are deliberately kept until ~2026-10-15 so the VM remains a
one-command rollback; step 3 stays open until then.

Before powering the VM off, every integration was re-verified as
pointing at 10.100.0.35: Sonarr, Radarr, Tautulli, seerr, Uptime Kuma,
Homepage, Traefik and the UDM PLEX port-forward.

Section 9 gains a decommission log recording two behaviours that cost
time to work out: Veeam turns a removed job include into an explicit
Exclude tombstone rather than deleting it, and a plain sqlite3
integrity_check on a Plex library DB fails with "unknown tokenizer:
collating" because the stock binary lacks Plex's FTS collation - that
is not corruption.

ESXi port-group counts corrected (LAN_100 7->6, DATA_50 4->3), verified
by counting NICs on powered-on VMs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

veeam.md

@@ -55,7 +55,7 @@
 | Backup workstation | Endpoint Agent | Yes | Warning |
 | Backup Joes Macbook | Endpoint Agent | Yes | Warning |
 
-**Backup VMs** includes: Plex, Ignition, HA, DOCKER. Deployarr is explicitly excluded.
+**Backup VMs** includes: Ignition, HA, DOCKER. Deployarr and Plex are explicitly excluded (Plex removed 2026-09-17 on decommission; Veeam converts a removed include into an explicit exclude rather than dropping the entry, so the tombstone is expected). `/opt/plex` is now covered by the DOCKER VM backup.
 
 **Backup WW_DEV_VM** includes: WW_DEV_VM (Wonderware dev VM, ~256 GB increments).