Don't wait for clock sync at boot, so the VM's sshd starts

Arch's cloud image enables systemd-time-wait-sync, and sshd is ordered
after pacman-init, which waits for time-sync.target. Once provision.sh
turns off systemd-networkd, systemd-timesyncd thinks it's offline and never
syncs, so every boot after the base build waited forever and the installed
image's build failed with "The VM didn't answer on SSH".

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

vm/provision.sh

@@ -44,6 +44,11 @@ systemctl disable systemd-networkd.service systemd-networkd.socket systemd-resol
 # systemd-resolved
 rm -f /etc/resolv.conf
 systemctl enable NetworkManager.service gdm.service sshd.service
+# Arch's cloud image makes boot wait until the clock has synced, and sshd
+# waits for that. Without systemd-networkd, systemd-timesyncd thinks it's
+# offline and never syncs, so sshd would never start. archinstall doesn't
+# turn this on, and QEMU sets the VM's clock from the host's.
+systemctl disable systemd-time-wait-sync.service
 
 echo "== Automatic login to GNOME as $USER_NAME"
 cat > /etc/gdm/custom.conf << EOF