[ResilienceManagement] Onboard read-only get commands (namespace: resilience)

[LavishSingal]

What does this PR do?

Onboards the new Azure Resilience Management toolset (Azure.Mcp.Tools.ResilienceManagement, command namespace resilience) as a new Azure MCP toolset.

This is PR 1 of the rollout plan in #2894 — the read-only surface across all command groups (all get commands). It establishes the toolset plumbing end-to-end (IAreaSetup, BaseAzureResourceService, non-standard serviceGroup path-parameter handling, pagination, parameter shapes, telemetry, and test scaffolding) with zero blast radius. Authoring (create-or-update) and lifecycle/action commands follow in PR 2 and PR 3 respectively.

All commands are read-only (ReadOnly = true, Destructive = false, Idempotent = true). Each get command returns details for a named resource, or lists resources (id + name only) when the name is omitted.

Commands added:

• Goal
  • resilience goal template get (GoalTemplates_List / GoalTemplates_Get)
  • resilience goal assignment get (GoalAssignments_List / GoalAssignments_Get)
  • resilience goal resource get (GoalResources_List / GoalResources_Get)
• Usage Plan
  • resilience usageplan get (UsagePlans_ListBySubscription / UsagePlans_ListByResourceGroup / UsagePlans_Get)
  • resilience usageplan enrollment get (Enrollments_List / Enrollments_Get)
• Drill
  • resilience drill get (Drills_List / Drills_Get)
  • resilience drill resource get (DrillResources_List / DrillResources_Get)
  • resilience drill run get (DrillRuns_List / DrillRuns_Get)
  • resilience drill run resource get (DrillRunResources_List / DrillRunResources_Get)
• Recovery
  • resilience recovery plan get (RecoveryPlans_List / RecoveryPlans_Get)
  • resilience recovery plan resource get (RecoveryResources_List / RecoveryResources_Get)
  • resilience recovery job get (RecoveryJobs_List / RecoveryJobs_Get)
  • resilience recovery job resource get (RecoveryJobResources_List / RecoveryJobResources_Get)

GitHub issue number?

Part of #2894

Pre-merge Checklist

• Required for All PRs
  • Read contribution guidelines
  • PR title clearly describes the change
  • Commit history is clean with descriptive messages (cleanup guide)
  • Added comprehensive tests for new/modified functionality
  • Created a changelog entry if the change falls among the following: new feature, bug fix, UI/UX update, breaking change, or updated dependencies. Follow the changelog entry guide
• For MCP tool changes:
  • One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
  • Updated servers/Azure.Mcp.Server/README.md and/or servers/Fabric.Mcp.Server/README.md documentation
  • Validate README.md changes running the script ./eng/scripts/Process-PackageReadMe.ps1. See Package README
  • For new or modified tool descriptions, ran ToolDescriptionEvaluator and obtained a score of 0.4 or more and a top 3 ranking for all related test prompts
  • For tools with new names, including new tools or renamed tools, update consolidated-tools.json
  • For renamed tools, follow the Tool Rename Checklist and tag the PR with the breaking-change label
  • For new tools associated with Azure services or publicly available tools/APIs/products, add URL to documentation in the PR description
• Extra steps for Azure MCP Server tool changes:
  • Updated command list in servers/Azure.Mcp.Server/docs/azmcp-commands.md
  • Ran ./eng/scripts/Update-AzCommandsMetadata.ps1 to update tool metadata in azmcp-commands.md (required for CI)
  • Updated test prompts in servers/Azure.Mcp.Server/docs/e2eTestPrompts.md
  • 👉 For Community (non-Microsoft team member) PRs:
    • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
    • Manual tests run: added comment /azp run mcp - pullrequest - live to run Live Test Pipeline