Description of problem:

mta-cli fails on Windows with mount error

Version-Release number of selected component (if applicable):

image 7.1.0-9 

How reproducible:

100% 

Steps to Reproduce:
1. Pull all images
2. Run a command like
`windows-mta-cli.exe analyze --input jee-example-app-1.0.0.ear --output D:\redhat\report --source weblogic --target eap7 --overwrite`

Actual results:

Command returnes an error, analysis doesn't happen  

Expected results:

Command should complete successfully.

Additional info:
C:\Program Files\RedHat\Podman\podman.exe run --rm --name lDcbzAuFiHBEvJId --entrypoint /usr/local/bin/mta-cli --env RUN_MODE=container registry.redhat.io/mta/mta-cli-rhel9:7.1.0 analyze --list-sourcesC:\Program Files\RedHat\Podman\podman.exe run --rm --name kdEGkqGALIeuRqLq --entrypoint /usr/local/bin/mta-cli --env RUN_MODE=container registry.redhat.io/mta/mta-cli-rhel9:7.1.0 analyze --list-targetsTgoOubWSApvjelJA
aAqvjlKpeGuUPTyr

time="2024-07-08T14:30:56+02:00" level=info msg="starting first provider" provider=java
C:\Program Files\RedHat\Podman\podman.exe run -d --rm --name vYFoMeFRuWdYpvJV --network TgoOubWSApvjelJA -v aAqvjlKpeGuUPTyr:/opt/input/source/jee-example-app-1.0.0.ear registry.redhat.io/mta/mta-java-external-provider-rhel9:7.1.0 --port=50828Error: mounting volume aAqvjlKpeGuUPTyr for container 38cfcdaabbb8f2686c7cfdf15ca3773b0b04704b80c050193d1bafd1fae1c3ed: mount: /home/user/.local/share/containers/storage/volumes/aAqvjlKpeGuUPTyr/_data: special device D:\cli does not exist.
dmesg(1) may have more information after failed mount system call.