feat: land first grounded depth tranche progress

[TacoRocket]

What Changed

This PR lands the first completed grounded post-Phase-3 follow-on progress now ready for review:

• deepen api-mgmt for Azure API Management with subscription, named-value, Key Vault, and backend-host triage cues
• deepen aks for Azure Kubernetes Service with Azure-side federation and managed-surface cues such as OIDC, workload identity, add-ons, and web app routing
• define the v1.1.0 tranche boundary as the release after the grounded post-Phase-3 follow-ons are complete

Why

AzureFox v1.0.0 shipped the initial Phase 1 through Phase 3 command surface. These changes start the next backward-compatible depth tranche without crossing the command boundary into raw config dumping, secret retrieval, or Kubernetes deep-dive behavior.

The operator impact is:

• api-mgmt better answers which Azure API Management service deserves follow-up first
• aks better answers whether a cluster is worth pivoting into a separate Kubernetes-focused tool
• the release boundary for v1.1.0 is now explicit in repo docs and the external handover

Validation

• python3 -m ruff check src/azurefox/models/common.py src/azurefox/collectors/provider.py src/azurefox/render/table.py src/azurefox/help.py tests/test_models.py tests/test_collectors.py tests/test_terminal_ux.py tests/test_help.py
• PYTHONPATH=src python3 -m pytest tests/test_collectors.py tests/test_terminal_ux.py tests/test_help.py tests/test_models.py tests/test_golden_outputs.py tests/test_contract_schemas.py -q

Notes

• this PR intentionally stops short of full Azure API Management policy-body export or secret retrieval
• this PR intentionally keeps aks on Azure-native cluster posture and leaves Kubernetes-object deep dives to a separate tool/workflow
• the next grounded follow-on candidate remains acr-depth