Add Connection-specific DNS Suffix for WSL2 reachable networks to resolv.conf

Nobody has claimed this yet.

**Is your feature request related to a problem? Please describe.**
Currently there's some mangling done by (probably) Windows virtual switch/DNS resolver? Not all DNS queries that work with Windows work in WSL2. For what's not working usually helps if I just add that specific Connection-specific DNS Suffix as `search SUFFIX` and eventually any domains from connection DNS Search List to `/etc/resolv.conf`.

In situations where I can use e.g. `ping host` on Windows I need to use `ping host.fully.qualified.domain.name` in WSL2 which is sometimes annoying.

**Describe the solution you'd like**
I'd like if `init` (or even better; some Windows side thing when connectivity changes re-) generated `/etc/resolv.conf` so that all known DNS lookup suffixes are automatically added as `search` stanzas. Maybe this could be sub-option of whether or not to generate `resolv.conf`.

**Describe alternatives you've considered**
Currently I am using simple script that is triggered by Windows Scheduler; Event type "Microsoft-Windows-NetworkProfile/Operational" and "Event Id" 1000. Script utilizes lame Powershell query to get suffixes:

``` powershell
Write-Host search @(Get-DnsClient | Select-Object -Property ConnectionSpecificSuffix | Where-Object {\$_.ConnectionSpecificSuffix -ne \"\"} | %{\$_.ConnectionSpecificSuffix})")
```

**Additional context**
I believe if WSL has access to network it should behave same (in terms of DNS resolver and other aspects) as host OS.

Start with the init path that generates /etc/resolv.conf and inspect how connectivity changes are handled. Compare its behavior with the supplied PowerShell Get-DnsClient query and NetworkProfile event 1000; done means connection-specific DNS suffixes appear as search entries in resolv.conf after network changes.

Written by the indexing model from the issue text.