fix: revert upgrade some telemetry related dependencies

[JasonYeMSFT (JasonYeMSFT)]

What does this PR do?

[Provide a clear, concise description of the changes]

I was investigating a mysterious telemetry event drop from plugin-telemetry command since Aug. 19th. My experimentation makes me believes that Azure MCP introduced a regression in 3.0.0-beta.36 release causing it to randomly drop such telemetry events.

My reproduction steps:

1. Set up HTTP tracer (e.g. Fiddler) to capture telemetry events sent to the expected data sink (centralus-2.in.applicationinsights.azure.com)
2. Install azure plugin with the hook script and prepare to load it in Copilot CLI
3. Edit the hook script to pin the azure mcp version in the npx command and see if the PluginExecuted events consistently show up in the tracer

My testing result shows that azure mcp can consistently send those PluginExecuted events at 3.0.0-beta.34 and 3.0.0-beta.35. Starting from 3.0.0-beta.36, from what I can see in the tracer, azure mcp start randomly not sending those events or only sending a subset of them.

I couldn't find code change in Azure MCP that caused this. The most promising change that would have caused this was the dependency upgrade for these two packages. I reverted their versions, rebuild Azure MCP with -c Release, pinned the hook to use this locally built exe and verified that I can consistently see Azure MCP sending the PluginExecuted events if I retry the same steps above.

I would like to downgrade these packages to hopefully mitigate the telemetry data loss. We will need to further investigate the root cause of the regression so we won't be stuck with these package versions.

[Add additional context, screenshots, or information that helps reviewers]

GitHub issue number?

[Link to the GitHub issue this PR addresses]

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

[Tom Meschter (tmeschter)]

/azp run mcp - pullrequest

[Alan Zimmer (alzimmermsft)]

/azp run mcp - pullrequest

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).