Support advanced mDNS hostnames (multiple local TLDs, nested subdomains, and wildcard domains)

### Description of the new feature / enhancement

PowerToys currently provides convenient local development utilities, but
mDNS support is still limited compared to what many developers and
homelab users expect.

### Proposed capabilities

1. **Support multiple local domain suffixes**

In addition to `.local`, allow users to register and resolve other local domain suffixes, such as:

- `.lan`
- `.home`
- `.internal`
- `.netdev`

2. **Support nested subdomains**, for example:

```
app.home
api.home
service.dev.home
api.backend.home
node01.cluster.home
```

3. **Support wildcard domains**, for example:

```
*.home
*.dev.home
*.internal
```

Any matching subdomain should automatically resolve to the local machine.

### Scenario when this would be used?

- Local ASP.NET / Node.js development
- Docker Compose
- Kubernetes
- Reverse proxies (Nginx, Caddy, Traefik, IIS)
- Homelab
- Microservices
- Embedded development

This would eliminate frequent editing of the Windows hosts file and
improve developer productivity.

### Supporting information

Modern development platforms increasingly rely on hostname-based routing
rather than port-based routing.

Supporting hierarchical hostnames and wildcard domains would make
PowerToys a lightweight local DNS solution for Windows developers while
keeping configuration simple.

No implementation files, entry points, or tests are named. Start by locating PowerToys' existing mDNS or local-hostname support and review the issue discussion, then define tests for multiple suffixes, nested names, and wildcard matching; done means supported names resolve to the local machine without hosts-file edits.

Written by the indexing model from the issue text.