`Start-OSDCloud`: Windows ESDs do not get cached to USB when using newer `-OSName` parameter

[ITistheworst]

Describe the bug
If you run Start-OSDCloud using the newer -OSName parameter, or without specifying any specific version/build and allowing OSDCloud to select the latest available build, the ESD Windows download is never cached to the USB media. As a result, the ESD is re-downloaded on every deployment.

Choosing the same build via the legacy parameters -OSBuild and -OSVersion caches the windows ESD correctly and re-uses it on subsquent deployments.

To Reproduce
Steps to reproduce the behavior:

1. Boot OSDCloud media
2. Run Start-OSDCloud with -OSName or no OS version parameters

Expected behavior
Windows build should be cached to USB for faster subsequent builds/lower network traffic

Additional context

• No error or warning is shown when the image is not cached; the caching step is just silently skipped.
• The same behavior occurs if the USB drive is not formatted as NTFS.
• The issue does not occur when using the legacy -OSBuild and -OSVersion parameters.

[ITistheworst]

Looks like PR #362 would address this