fix(nests): use moq-auth.nostrnests.com for JWT mint

The previous defaults pointed both `service` and `endpoint` URLs at
`moq.nostrnests.com:4443`. That host only listens on UDP/QUIC for the
WebTransport relay — TCP :4443 is unreachable. OkHttp can't speak HTTP/3,
so the JWT-mint POST hangs and fails with `ConnectException`, leaving
the room screen stuck on "Reconnecting".

The real nostrnests deployment co-locates auth and relay on different
hosts (verified against the production NestsUI bundle):

    relay (WebTransport, QUIC only):  https://moq.nostrnests.com:4443
    auth  (JWT mint, regular HTTPS):  https://moq-auth.nostrnests.com

Split the defaults accordingly and add a `resolveServerPair` helper that
maps a single saved kind-10112 URL onto the (service, endpoint) pair the
kind-30312 event needs. The helper recognises both the auth-host and
the legacy relay-host the prior defaults wrote, so users upgrading from
the broken version migrate transparently the next time they open the
create-room sheet. Community deployments that genuinely co-locate keep
working via the fallback.

Update the recommended-servers list and the kind-10112 documentation to
match: the stored `server` URL is the moq-auth base (the URL that ends
up in the kind-30312 `service` tag).

quartz/src/commonMain/kotlin/com/vitorpamplona/quartz/nip53LiveActivities/nestsServers/NestsServersEvent.kt

@@ -42,19 +42,23 @@ import com.vitorpamplona.quartz.utils.TimeUtils
  *       "kind": 10112,
  *       "tags": [
  *         ["alt", "Audio-room (nests) MoQ servers used by the author"],
- *         ["server", "https://moq.nostrnests.com"],
+ *         ["server", "https://moq-auth.nostrnests.com"],
  *         ["server", "https://moq.example.org"],
  *         ...
  *       ],
  *       "content": ""
  *     }
  *
- * The `server` URL points at the moq-rs / moq-auth deployment's base
- * URL — Amethyst's `CreateNestSheet` uses it for both the
- * `service` (auth sidecar) and `endpoint` (WebTransport relay) tags
- * on the kind-30312 event, since nostrnests's reference deployment
- * co-locates them. A future revision can split the two into separate
- * tag fields if the community pulls them apart.
+ * The `server` URL is the moq-auth (JWT mint) base — that's also the
+ * URL that goes into the kind-30312 `service` tag. The matching
+ * WebTransport relay endpoint is NOT part of this list; reference
+ * deployments like nostrnests run the auth sidecar on regular HTTPS
+ * (e.g. `https://moq-auth.nostrnests.com`) and the QUIC relay on a
+ * separate host/port (e.g. `https://moq.nostrnests.com:4443`), so
+ * Amethyst's `CreateNestSheet` resolves the pair via a known-deployment
+ * mapping (with a fallback that reuses the saved URL for both tags
+ * when a community deployment genuinely co-locates them). A future
+ * revision can split the two into separate tag fields if needed.
  *
  * This event is shaped 1:1 after `BlossomServersEvent` (kind 10063,
  * NIP-B7) so existing list-state / settings UI patterns translate