[IMPROVEMENT] Option to treat &ampersand as literal in cli path arguments

### Please confirm these before moving forward.

- [x] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- [x] This improvement refers to an existing feature. If you want to suggest a new feature, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=new-feature&projects=&template=feature-request.yml&title=%5BFEATURE+REQUEST%5D+%28Enter+your+description+here%29).
- [x] This improvement is not a bug. If you want to report a bug, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=bug&projects=&template=bug-issue.yml&title=%5BBUG%5D+%28Enter+your+description+here%29).

### Describe the improvement

(not 100% sure whether this is a bug as I don't fully understand what the relevant syntax UniGet uses in this context since I couldn't find an escape char and a similar bug was already fixed https://github.com/Devolutions/UniGetUI/issues/3904)

When passing `--location` to WinGetCli, I'd like to have an option to treat `&` ampersand char as literal so that `--location "C:\Program Files\App&Name"` will use the `App&Name` as the directory name.

(It seems that currently UniGetUI uses some syntax that doesn't allow that, though I couldn't figure out how to escape it either, which should be possible in a syntax, `""a&b`&c^&d~&e\&'&'&&""` didn't work to produce a single `&` in the command-line to run box)

### Describe how this improvement could help users

Not worrying about `&`ampersands in their paths

Start at the --location handling for WinGetCli and compare its argument parsing with issue #3904. Determine how the command-line-to-run box currently treats ampersands and define an option or escaping rule that preserves an ampersand in a path; done means a path such as C:\Program Files\App&Name reaches WinGetCli unchanged.

Written by the indexing model from the issue text.