[Onboard] Support MCP Tools for Azure Terraform

[liuwuliuyun]

What does this PR do?

Adds a new Azure Terraform toolset to the Azure MCP Server with 10 tools across 5 functional areas:

• AzureRM Provider Docs (azureterraform_azurerm_get) — Retrieve AzureRM provider documentation for Terraform resources
• AzAPI Provider Docs (azureterraform_azapi_get) — Retrieve AzAPI provider documentation for Azure resources by resource type and API version
• Azure Verified Modules (AVM) (azureterraform_avm_list, azureterraform_avm_versions, azureterraform_avm_get) — List, query versions, and retrieve documentation for Azure Verified Modules
• Azure Export for Terraform (aztfexport) (azureterraform_aztfexport_resource, azureterraform_aztfexport_resourcegroup, azureterraform_aztfexport_query) — Generate aztfexport commands to export Azure resources to Terraform configuration
• Conftest Policy Validation (azureterraform_conftest_workspace, azureterraform_conftest_plan) — Generate conftest commands to validate Terraform configurations against Azure policies

These tools are bundled in a single PR because they form a cohesive toolset for Terraform workflows on Azure, sharing common models, services, and infrastructure. Splitting them would create artificial boundaries within tightly coupled code.

Azure Terraform documentation:

• AzureRM Provider: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs
• AzAPI Provider: https://registry.terraform.io/providers/Azure/azapi/latest/docs
• Azure Verified Modules: https://azure.github.io/Azure-Verified-Modules/
• Azure Export for Terraform: https://learn.microsoft.com/en-us/azure/developer/terraform/azure-export-for-terraform/overview
• Conftest: https://www.conftest.dev/

GitHub issue number?

#2215

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
    • N/A: These 10 tools form a tightly coupled toolset sharing common models, services, and infrastructure. Bundled intentionally.
  • 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
    • N/A: No tools renamed.
  • 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