docs: add address resolver how-to guide

[Aryex]

Summary

Add documentation for the address resolver feature across clients.

⚠️ Attention: This PR was generated automatically. Verify that all relevant pages have been updated.

Source Commits

• Java — 24adccb (valkey-io/valkey-glide@24adccb): Support custom socket address resolution, #5328
• Python — b4b34a1 (valkey-io/valkey-glide@b4b34a1): Python: Support custom socket address resolution, #5876
• Node.js — c53df65 (valkey-io/valkey-glide@c53df65): Node: Support custom socket address resolution when connecting to valkey, #5890
• Go — 79a1551 (valkey-io/valkey-glide@79a1551): Go: Support custom socket address resolution, #5891
• C# — 7a822d4 (valkey-io/valkey-glide-csharp@7a822d4): Support custom socket address resolution, #392
• PHP — 8f00aae (valkey-io/valkey-glide-php@8f00aae): feat: add address resolver support for standalone and cluster clients, Add JSON module commands docs #196

Changes

• Added new how-to page: how-to/connections/address-resolver.mdx
• Covers basic usage, fallback behavior, and cluster client usage

Context

The resolver intercepts host/port resolution at connection time, enabling DNS overrides, service mesh scenarios, and testing with fake addresses. If the resolver throws or returns invalid data, the client gracefully falls back to the original address.

cc @affonsov

---

This PR was generated by the automated documentation pipeline.

[Aryex]

📝 Updated PR description with 7a822d4 — Support custom socket address resolution (#392)

Added C# code examples to the address resolver how-to page covering basic usage, fallback behavior, and cluster client configuration.

[Aryex]

Updated docs with examples from other clients language