feat(talos): hcloud nodes carry ens19 as a dummy link

The v30iot NetworkAttachmentDefinitions of matter-server, music-assistant,
otbr, shelly-manager and the mdns relay name master: ens19. On the hcloud
site no such link existed, so macvlan creation failed outright. Each hcloud
node now declares ens19 as a DummyLinkConfig: no address, nothing behind it.

The NADs lease by DHCP, and nothing answers on a dummy link, so the pods get
their macvlan but the dhcp IPAM step still times out.

Validated: talosctl gen config (cluster + site-hcloud + hcloud-1) then
talosctl validate --mode cloud --strict.

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

kubernetes/talos/patches/hcloud-1.yaml

@@ -55,6 +55,13 @@ kind: LinkConfig
 name: ceph-san
 up: true
 ---
+# The v30iot macvlan parent the NADs name (master: ens19). Hetzner has no IoT
+# VLAN, so it is a dummy link: no address, nothing behind it.
+apiVersion: v1alpha1
+kind: DummyLinkConfig
+name: ens19
+up: true
+---
 # Capped so the OSD partition fits beside it on cpx52's 480 GB local disk.
 apiVersion: v1alpha1
 kind: VolumeConfig

kubernetes/talos/patches/hcloud-2.yaml

@@ -42,6 +42,12 @@ up: true
 ---
 # See hcloud-1.yaml.
 apiVersion: v1alpha1
+kind: DummyLinkConfig
+name: ens19
+up: true
+---
+# See hcloud-1.yaml.
+apiVersion: v1alpha1
 kind: VolumeConfig
 name: EPHEMERAL
 provisioning:

kubernetes/talos/patches/hcloud-3.yaml

@@ -42,6 +42,12 @@ up: true
 ---
 # See hcloud-1.yaml.
 apiVersion: v1alpha1
+kind: DummyLinkConfig
+name: ens19
+up: true
+---
+# See hcloud-1.yaml.
+apiVersion: v1alpha1
 kind: VolumeConfig
 name: EPHEMERAL
 provisioning: