System-wide WingetUI installation

[marticliment]

Due to the integration of .net code (more migration will be done soon) and some incompatiblities with winget.exe, future versions of WingetUI will require a path that does not contain non-ascii characters. To achieve so, WingetUI will now be installed to the "Program Files" folder.

However, as discussed in some issues on this same issue, some components (a.k.a. choco-cli) require to be located on non-admin writeable locations, hence why WingetUI was previously installed in a per-user basis.
This is why the WingetUI installation has been split into two parts:

• One placed under Program Files, providing the core code of WingetUI and all the components that don't require write access
• One located under %localappdata%\Programs\WingetUI, containing the chocolatey files and future components that may require administrator rights.

This change will fix all the issues with .net crashing WingetUI due to null pointers, as well as "Permission denied" issues.
Furthermore, will add increased security, since core components will require administrator rights to be modified.

NOTE: Users without administrator privileges will be able to still use a portable installation.

NOTE: Portable installations will work as usual. If a portable installation is done, user-based components will be extracted alongside with WingetUI in the desired directory

fix #1226
fix #1229
fix #1230
fix #1239
fix #1245

fix #1222
fix #1125

related to #712 - This change increases .net compatibility, which will allow substantial winget improvements