feat: User experience enhancement of az aks agent

[nilo19]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az aks agent

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Enhance the user experience of az aks agent, including:

1. Use aks-mcp by default, offering an opt-out flag --no-aks-mcp.
2. Disable duplicated built-in toolsets when using aks-mcp.
3. Manage the lifecycle of aks-mcp binary, including downloading, updating, health checking and gracefully stopping.
4. Offer --status to display the system status.
5. Refine system prompt.
6. Smart toolset refreshment when switching between mcp and traditional mode.

[azure-client-tools-bot-prd]

Validation for Breaking Change Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Hi @nilo19,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[Copilot]

Pull Request Overview

This PR enhances the user experience of the az aks agent command by introducing MCP (Model Context Protocol) support as the default mode, adding a new --status flag for system monitoring, and improving the overall agent lifecycle management.

• Introduces aks-mcp as the default mode with an opt-out flag --no-aks-mcp
• Adds comprehensive status reporting via --status flag
• Implements lifecycle management for MCP binary including downloading, updating, and health checking

Reviewed Changes

Copilot reviewed 27 out of 28 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
custom.py	Adds new parameters and status command implementation
test_aks_agent_status_registration.py	Tests for status command registration
test_user_feedback.py	Tests for progress reporting and user feedback
test_mcp_manager.py	Tests for MCP manager lifecycle operations
test_config_generator.py	Tests for configuration generation
test_binary_manager.py	Tests for binary management operations
test_aks_agent_status_models.py	Tests for status data models
test_aks_agent_status_command.py	Tests for status command functionality
test_aks_agent_status.py	Tests for status collection logic
test_aks_agent_smart_refresh.py	Tests for smart refresh strategy
test_aks_agent_parameters.py	Tests for new parameter parsing
test_aks_agent_mcp_integration.py	Tests for MCP integration functionality
test_aks_agent_error_handler.py	Tests for enhanced error handling
user_feedback.py	Progress reporting implementation
status_models.py	Data models for status information
status.py	Status collection and management logic

[github-actions]

• For more info about extension versioning, please refer to Extension version schema