podman machine wsl startup flake

[Luap99]

https://github.com/podman-container-tools/podman/actions/runs/27942527789/job/82680657124
https://github.com/podman-container-tools/podman/commit/c271cbdd1f92d4510810373cdc8a9cad61dc6d99/checks/82680657124/logs

D:/a/podman/podman/pkg/machine/e2e/basic_test.go:27
  Basic ops
  D:/a/podman/podman/pkg/machine/e2e/basic_test.go:28
  > Enter [BeforeEach] TOP-LEVEL - D:/a/podman/podman/pkg/machine/e2e/machine_test.go:218 @ 06/22/26 09:30:13.569
  < Exit [BeforeEach] TOP-LEVEL - D:/a/podman/podman/pkg/machine/e2e/machine_test.go:218 @ 06/22/26 09:30:13.728 (159ms)
  > Enter [It] Basic ops - D:/a/podman/podman/pkg/machine/e2e/basic_test.go:28 @ 06/22/26 09:30:13.728
  D:\a\podman\podman\bin\windows\podman.exe machine init --disk-size 11 --image C:\Users\RUNNER~1\AppData\Local\Temp\podman-machine.x86_64.wsl.tar --now be4f69e5ca05
  Importing operating system into WSL (this may take a few minutes on a new WSL install)...
  The operation completed successfully. 
  Configuring system...
  Machine init complete
  Starting machine "be4f69e5ca05"

  This machine is currently configured in rootless mode. If your containers
  require root permissions (e.g. ports < 1024), or if you run into compatibility
  issues with non-podman clients, you can switch using the following command:

  	podman machine set --rootful be4f69e5ca05

  API forwarding listening on: npipe:////./pipe/podman-be4f69e5ca05

  Another process was listening on the default Docker API pipe address.
  You can still connect Docker API clients by setting DOCKER HOST using the
  following powershell command in your terminal session:

  	$Env:DOCKER_HOST = 'npipe:////./pipe/podman-be4f69e5ca05'

  Or in a classic CMD prompt:

  	set DOCKER_HOST=npipe:////./pipe/podman-be4f69e5ca05

  Alternatively, terminate the other process and restart podman machine.
  Machine "be4f69e5ca05" started successfully
  D:\a\podman\podman\bin\windows\podman.exe machine ssh be4f69e5ca05 cat /etc/containers/podman-machine-tmpfile
  cat: /etc/containers/podman-machine-tmpfile: No such file or directory
  [FAILED] Expected
      <int>: 1
  to match exit code:
      <int>: 0
  In [It] at: D:/a/podman/podman/pkg/machine/e2e/basic_test.go:52 @ 06/22/26 09:30:57.856

Is it possible that WSL does not wait for systemd to be fully booted in the namespace? i.e. the mount is created as a systemd unit which has Before=podman.socket even set. So I guess the ssh command might either run to early where the systemd unit has not finished mounting or the systemd unit failed to mount it for some reason.