Remove unused provider selectors from workflows

[danivilla9]

We have some workflows that include an option for podman provider in the workflow_dispatch input, but they never use that value. Examples of this that I found are:

• PD E2E with Podman Latest HyperV https://github.com/podman-desktop/e2e/actions/workflows/podman-desktop-e2e-nightly-windows-hyperv.yaml
• PD E2E with Podman Nightly WSL https://github.com/podman-desktop/e2e/actions/workflows/podman-desktop-e2e-nightly-windows-wsl.yaml
• PD E2E Podman Latest Kubernetes https://github.com/podman-desktop/e2e/actions/workflows/podman-desktop-e2e-kubernetes.yaml

I think that the workflows should be checked for similar cases and the unused inputs should be removed for more clarity in the code and in the usage

[odockal]

@danivilla9 Are you sure? The first workflow has this code here: https://github.com/podman-desktop/e2e/actions/runs/18928066347/workflow#L96, which could imply that provider is taken from the input.

Or what do you have in mind? Looking at the manual run: https://github.com/podman-desktop/e2e/actions/runs/18750970665/job/53490202570#step:10:310, the hyperv got it.

at the same time, workflow has hyperV in its name. so it is kinda confusing. I am testing mentioned wf with wsl provider: https://github.com/podman-desktop/e2e/actions/runs/18941085024.

[danivilla9]

My point is that, if the idea of the first two workflows is to have two separate ways of running the same tests, with the same setup, except for the podman provider, deleting the input and hardcoding the provider is a good approach.

Having the option to change the provider just gives the user more mental load, because yes, technically you can run the hyperv workflow with the wsl provider, but what you should do is run the wsl workflow with the wsl provider and the hyperv workflow with the hyperv provider so that the workflow runs are sorted properly in a cohesive way. So, unless I'm missing something:

• Those inputs are never used
• If they are used, I think it's wrong to do so
• It makes the use of the workflow confusing