[Meta] Handle or resolve Windows Compatibility Issues like hosts file/privilege escalation

[rickmanelius]

This is a follow-up to #196 (comment), specifically with respect to the following:

Windows Compatibility: Addressing areas where linux/macOS assumptions fail (/etc/hosts, linux commands, .exe naming convention requirements on Windows, etc.).

• Currently we check for the existence of the sudo command, and if it is found, use it to escalate privileges to add an entry to the /etc/hosts file. This is not a valid technique on Windows native, as sudo is not available and privilege escalation is done in other ways.
• The purpose for the privilege escalation is to edit the hosts file, which is at /Windows/System32/drivers/etc/hosts instead of /etc/hosts. It's our belief that the hosts management library we're using can actually handle this on windows if we have a good privilege escalation technique.

Related source links or issues:

• Parent issue: Decisions and Plan for Linux & Windows Support #196 (comment)
• Discussion of providing a wildcard DNS entry to serve this function: Use wildcard FQDN for ddev sites instead of manipulating /etc/hosts (most of the time) #175

[rickmanelius]

This seems very much related to #511. Closing this item in favor of continuing the conversation there.