Consul support for Envoy on Windows

#### Feature Description

We’re looking for feedback on use cases and patterns for Consul support of Envoy on Windows. Envoy on Windows is now [generally available](https://blog.envoyproxy.io/general-availability-of-envoy-on-windows-267e4544994a).

#### Use Case(s)

If you would like to use Consul with Envoy on Windows, please :+1: and add a comment with your use case answering the following:

- Would you be running Consul __servers__ on Windows?
- Would you be running Consul __gateways__ on Windows (mesh, api gateway, or terminating)?
- Would applications be running on Windows __VMs or containers__?
- Would applications be running on Nomad or Kubernetes?
- What __Windows server versions__ would you be interested in? (This will also depend on Envoy’s support of Windows server.)
- Would you be using Consul capabilities outside of service mesh (i.e., service discovery, health checking, etc.)?

Any other information about the topology or architecture you’re looking to implement will help us determine how to best integrate Consul with Envoy on Windows.

Thank you!