Automatic installation of WSL fails

[l0rd]

Issue Description

If WSL isn't installed, and a user tries to run podman machine init on Windows, Podman tries to install WSL automatically. This flow is currently broken.

Steps to reproduce the issue

Steps to reproduce the issue

1. Disable the Windows feature VirtualMachinePlatform and reboot
2. (until Fix WSL checks and run unit tests in CI #25522 get merged) Build podman from PR Fix WSL checks and run unit tests in CI #25522
3. Run podman machine init

Describe the results you received

When machine init is run from an Admin terminal, the command fails with the error Error: could not enable Virtual Machine Feature: command dism [/online /enable-feature /featurename:VirtualMachinePlatform /all /norestart] failed: exit status 3010.

When machine init is run from a non-Admin terminal, the command fails because podman machine init is re-executed with elevated privileges and the hidden parameter --reexec. It fails when it tries to recreate the system connection with the same name (the system connection was already created before the WSL check).

Describe the results you expected

WSL should be enabled successfully

podman info output

OS: windows/amd64
provider: wsl
version: 5.5.0-dev

Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: Get "http://d/v5.5.0/libpod/_ping": dial unix /run/podman/podman.sock: connect: A socket operation encountered a dead network.

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting