feat(@angular/cli): add update guide mcp tool

[sinedied]

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
  • I couldn't find any existing MCP-related tests to update. I've used @modelcontextprotocol/inspector to test the feature.
• Docs have been added / updated (for bug fixes / features)
  • I couldn't find any existing MCP-related doc to update

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

No MCP tool to provide Angular update guidance.

What is the new behavior?

This PR introduces the update_guide MCP tool that provides the same update info as on https://angular.dev/update-guide but in a convenient way to be used by LLMs.

Does this PR introduce a breaking change?

• Yes
• No

Other information

The recommendations.ts is directly copied from https://github.com/angular/angular/blob/main/adev/src/app/features/update/recommendations.ts

I think a sync mechanism should be implemented, or the website could provide a JSON format that could loaded dynamically. I'm all open for suggestions regarding this, to make sure these files are synced.
Simplest idea I have: add a basic curl that fetches the files before building.

Also, regarding the windows parameter, I used Node.js platform detection to automatically infer it, but let me know if you would prefer to still have it as an option of the tool.

[clydin]

Thank you for the contribution.
However, before the introduction of an update based tool, the Angular team needs to consider how best to store, retrieve and structure update related information. Ideally, we would like to avoid duplication of information and also structure the information to provide maximum benefit to both developers and LLMs. Once these elements are put into place, we can then evaluate the introduction of an update based tool.