Revisit how crc/this helper starts background processes?

[cfergeau]

win32-background-helper triggers warnings from malware detectors, as what it's doing is probably similar to what some malware are doing.
We could revisit how processes are started in the background.
One approach could be to use https://github.com/apenwarr/fixconsole/blob/5a9f6489cc2959fbd7474e4429d33b32f096c9bd/fixconsole_windows.go#L30-L75 so that we can start unmodified binaries in the background without briefly showing a black console window

Another approach is to stop using a background windows task and a special process to start in the background, but to start the process we need on demand, and make use of https://github.com/containers/podman/blob/c3ab75ca459dc52661197c3dd42520bbd3317479/pkg/machine/wsl/wutil/wutil.go#L25-L29
If we go this way, we need to make sure

• there are no black console window shown when doing it
• that the process keeps running after crc.exe exits, and after the terminal window it was started from is closed
• that admin-helper still works (it needs elevated privileges)