[Bug]: Herd does not work within a Windows domain controlled environment

### Platform

Windows

### Operating system version

Windows 11 Pro - 23H2, Build 22631.3374

### System architecture

Windows

### Herd Version

1.0.1

### PHP Version

_No response_

### Bug description

We purchased a Herd Pro Teams licence to try and migrate more of our team to using local development, however, our users have found many major issues in trying to run Herd in our Windows environment. The most likely cause given there doesn't appear to be open issues reporting any of our issues is that all our users are non-administrator users which are managed inside a Windows domain-managed (syncing with our local domain controller).

Even when running the Herd installer and application with elevated Admin permissions we still get many problems, I'll list what we've discovered so far below but this isn't exhaustive as so much isn't working:

- [ ] App isn't set to be run as administrator by default - you have to remember to right click and launch as admin each time
- [ ] None of the binaries are added to the Windows path, meaning `php`, `herd`, `composer` ... commands don't work
- [ ] Unable to add a site, UI shows, but when you add it says successful, but no files get created
- [ ] When trying to load the Sites UI after attempting to add a site, it just infinitely loads/spins
- [ ] Annoyance: Each power shell command you run, we have to type in admin credentials to escalate. Most tasks (adding services, securing sites (we manually got this working eventually)....) run many separate commands meaning we have to type in admin credentials over and over (just getting Heard installed with MySQL and Redis took > 10 privilege escalations, securing a single Site took 6!).

### Steps to reproduce

Install on a Windows user (non-admin) account within a Windows domain-managed environment

### Relevant log output

_No response_