Inconsistent service naming — "Azure Resilience" vs "Azure Resiliency" causes customer confusion

## Customer impact

Customers using the Azure MCP Server for the `resilience` namespace encounter two
different names for the same capability within a single documentation article,
plus two different documentation URLs. This inconsistency undermines trust and
hurts discoverability: a customer searching for "Azure Resilience" and one
searching for "Azure Resiliency" can't tell whether these are the same product.

## Evidence

In the generated MCP tool documentation for the `resilience` namespace (v3.0.0-beta.23):

- Article title / H1: **"Azure MCP Server tools for Azure Resilience"**
- Intro paragraph: **"Azure Resiliency** is an Azure service ... see
[**Azure Resiliency**](/azure/resiliency/resiliency-overview)."

So the same namespace is referred to as both "Azure Resilience" and
"Azure Resiliency", and the doc link uses `/azure/resiliency/resiliency-overview`
while other regenerated output points at `/azure/resilience/`.

## What I need from the MCP team

Consider changing resilience namespace to resiliency to align with service name.

## Why upstream

The namespace name and any service branding/metadata originate in the MCP server
definition. Downstream documentation generation inherits whatever naming the
server surfaces, so a single authoritative answer here removes the confusion
across all generated docs.

@g2vinay FYI

Start with the MCP server definition for the resilience namespace and inspect the service branding or metadata that generates its documentation. Compare the namespace, displayed name, and URLs described in the issue, then regenerate or inspect the v3.0.0-beta.23 documentation to confirm one consistent Azure naming scheme.

Written by the indexing model from the issue text.