### What happened

`omarchy dns` misreports a **Custom** DNS configuration as **Cloudflare** (or **Google**) whenever the custom server list happens to *contain* `1.1.1.1` / `8.8.8.8`, even though the primary server is something else entirely.

`current_dns_provider()` in `bin/omarchy-dns` does substring matching on the whole server list, and the known-provider branches are tested before the `Custom` fallback:

```bash
if [[ -z $compact ]]; then
  echo "DHCP"
elif [[ $dns == *"cloudflare-dns.com"* || $dns == *"1.1.1.1"* || $dns == *"2606:4700:4700::1111"* ]]; then
  echo "Cloudflare"
elif [[ $dns == *"dns.google"* || $dns == *"8.8.8.8"* || $dns == *"2001:4860:4860::8888"* ]]; then
  echo "Google"
else
  echo "Custom"
fi
```

So a perfectly ordinary setup — a local/internal resolver first, a public resolver as secondary — is labelled as if it were the stock Cloudflare preset.

### Steps to reproduce

```console
$ sudo omarchy dns Custom
Enter your DNS servers (space-separated, e.g. '192.168.1.1 1.1.1.1'):
20.20.20.3 1.1.1.1

$ omarchy dns
Cloudflare        # expected: Custom
```

The configuration itself is written correctly and works — `/etc/NetworkManager/conf.d/20-omarchy-dns.conf` has `servers=20.20.20.3,1.1.1.1`, the NM profile has `ipv4.dns: 20.20.20.3,1.1.1.1`, `/etc/systemd/resolved.conf` has `DNS=20.20.20.3 1.1.1.1`, and `resolvectl status` confirms both servers on the link. Only the *reporting* is wrong.

### Expected

`omarchy dns` should report `Custom` for any server list that is not exactly one of the presets it writes itself.

### Why it matters beyond the label

The DNS picker in the settings menu reads its current selection from `omarchy dns`, so it shows **Cloudflare** as the active choice. From the user's side this reads as "Omarchy forgot my DNS setting" — and the natural reaction is to re-open the menu and set it again, which is exactly the dangerous move: selecting the (apparently already-active) Cloudflare entry runs the `Cloudflare)` branch, which overwrites the NM drop-in, every ethernet/wifi connection profile *and* `/etc/systemd/resolved.conf`, silently discarding the primary resolver. On a machine whose primary DNS is an internal/split-horizon resolver, that quietly breaks internal name resolution.

### Suggested fix

Match the *normalized set* of servers against the exact lists the `Cloudflare)` and `Google)` branches write, instead of asking whether a known IP appears anywhere in the list. Anything that isn't an exact preset match is `Custom` by definition, which also keeps the report honest if someone uses Cloudflare's servers in a different order or with only one of the pair.

### System

- Omarchy 4.0.2-1 (bug also present on `quattro` — `bin/omarchy-dns` there is byte-identical to the installed `/usr/share/omarchy/bin/omarchy-dns`)
- Kernel 7.1.9-arch1-2, networkmanager 1.58.1-1, systemd 261.2-1
- AMD Ryzen 7 5800X / Radeon RX 6800 XT (Navi 21)