imaging: force shopfloor unattend deploy (was force:no -> went stale)

The shopfloor unattend deploy used force:no, so once a live copy existed the
playbook never overwrote it. That let the live gea-shopfloor unattend drift for
weeks - missing the Fetch + Verify-And-Heal staging steps - which is why imaging
lost payloads (CMM bundle/backups). Flip to force:yes so the repo stays the
source of truth, matching the standard/engineer unattend task.

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

playbook/pxe_server_setup.yml

@@ -685,7 +685,11 @@
         src: "{{ usb_mount }}/FlatUnattendW10-shopfloor.xml"
         dest: "{{ samba_share }}/{{ item }}/Deploy/FlatUnattendW10.xml"
         mode: '0644'
-        force: no
+        # force: yes - repo is source of truth. force: no let the live shopfloor
+        # unattend go stale (missing the Fetch + Verify-And-Heal staging steps),
+        # and a playbook run never repaired it. Keep it in sync like the standard
+        # /engineer unattend below.
+        force: yes
       loop: "{{ shopfloor_types }}"
       ignore_errors: yes