This PR is uses windows powershell to create `crc daemon` as task
and start it on demand for the current user. This doesn't need any
elevated privillages to run `crc daemon` for user context. It try to
perform following tasks
- Check if there is already crcDaemon task
    + If present does it the latest one using version info
- Install the task using predefined xml definition
- Start the task which run the `crc daemon` in background.

There is a known issue with windows powershell when you start a task
in background using `powershell.exe` then for a second the windows pops
up and disappear, PowerShell/PowerShell#3028
have more details around it but as of now this is only the way for
interactive user context otherwise the task will need the admin
privillages which we want to avoid.

Admin helper service is created and started when installer is used.
Some of the issue we are getting is user directly try to use crc
from command line and see if the openshift routes are mapped in hosts
file. This PR is help to detect if the service is running and it doesn't
need any privilage permission but it doesn't create or start this
service because that need administrator privilages.

…ecks

This PR will remove the crc daemon schedule task during the
uninstallation, as of now even with this PR when the task is running
and user try to uninstall then uninstaller warn user that `crc` binary
in used and user have option to forceful stop it and carry on or go
to task manager and kill it manually.

This PR remove preflight checks for daemon command because daemon can
run independent of a crc setup. the actual check happens when you
perform a `crc start`. Since those tests run as part of crc daemon which
takes around 5-6 sec so initial api response become block for 5-6 sec.

Without this PR following scenario happen
- User installed the crc first time and do the setup
- As part of the setup crc daemon is started by task schedular
- User reboot
- Tray autostart with reboot but `crc setup --check-only` fails
because daemon task is not running.

With this PR, check for daemon task running should first validate
if an existing process of `crc daemon` is running and the version
it get from the api should be same as the binary then task running
check succeed. So this PR will makes `crc setup --check-only` work
again with tray autostart.