Monitor detail header omits target for non-HTTP monitor types (TCP, DNS)

**Describe the bug**

In the web UI's monitor detail/header, TCP and DNS monitors do not display their primary target in the subtitle. The subtitle shows only the monitor type(e.g. "TCP monitor" / "DNS monitor") with no indication of the host:port being checked or the DNS record being resolved. Users have to open the edit dialog to confirm what the monitor is actually pointed at, which makes a dashboard of many similar-typed monitors hard to scan.

This may also apply to other monitor types, but thus far I've confirmed it applies to these two, and does _not_ apply to http and http-keyword.

**Database**
postgresql

**To Reproduce**
Steps to reproduce the behavior:

1. Create a TCP monitor pointing at e.g. 1.1.1.1:443.
2. Create a DNS monitor resolving e.g. example.com A record against 8.8.8.8.
3. Open the TCP monitor's detail page → header subtitle shows only TCP monitor — the host 1.1.1.1:443 is not displayed.
4. Open the DNS monitor's detail page → header subtitle shows only DNS monitor — the queried record / resolver are not displayed.
5. Same effect on the dashboard list cards: TCP and DNS rows do not surface their target.

**Expected behavior**
TCP and DNS monitors should surface their primary target in the header subtitle and list cards, e.g.:

- TCP → TCP monitor for 1.1.1.1:443
- DNS → DNS monitor for example.com (A @ 8.8.8.8)

The exact field used per type should be the most identifying configured value for that type.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: Windows 11, also reproduced on Debian 13
- Browser: Edge
- Version: 149

**Additional context**

- Likely a switch (monitor.type) in the header/title component that has cases for some monitor types but falls through to a generic "{Type} monitor"string for TCP/DNS (and possibly other non-HTTP types — worth auditing).
- Workaround: open the edit dialog to see the target — fine for a few monitors, painful for a dashboard with many similarly-typed ones.

Find the UI component that renders the monitor detail header and list cards, likely in a frontend directory. Look for a switch statement on monitor.type that formats the subtitle. Identify where TCP and DNS monitor data (host:port, record, resolver) is fetched from the backend. Add cases for these types to display the target, then test by creating TCP and DNS monitors and checking the UI.

Escrito por el modelo de indexación a partir del texto del issue.