Fix reMarkable's fundamental failings

The following is for a Configuration Manager install.
I am making this a "new" app as that's my best guess for category.

reMarkable's EXE installer inherently installs as a "per user" install, but REQUIRES local admin, and places the files in C:\Program Files.

"The reMarkable desktop app installer is an EXE built on Qt Installer Framework and, in current manifests, is published as user‑scope (per‑user) rather than machine‑scope. Wingetly’s page for v3.29.0 explicitly lists the installer Scope = user"

The design of the installer is fundamentally antithetical to enterprise deployment.
This is very stupid and bad, and even the updater requires admin, so having Recast keep it up to date is great!
Except.
It's installing for System, which it has to do for the admin privs, but then registers the Start Menu Shortcut and Add Remove registry entries into the USER (HKU) registry of NTUSER:SYSTEM.
So, for this to be deployed with Config Manager and actually be usable by the end user, you need to copy the shortcut into the system-wide start menu ( C:\ProgramData\Microsoft\Windows\Start Menu\Programs) so that users can actually use the app after the install. I don't know if pre- and Post- install scripts are something you can supply via the application catalog, but yeah. reMarkable's desktop app springs eternal with annoyance and failure. I can just add the scripts myself, but figured y'all should know that the install doesn't really "work" as it stands.