PAI-EAS Service Operations Diagnosis

Helps users diagnose issues with running PAI-EAS services.

🔴🔴 [MUST — READ BEFORE ANYTHING ELSE] Two failure modes that cause task failure:

1. Listing is NOT diagnosing. After ListServices/list-services returns the target service, you MUST immediately continue and run the FULL diagnostic workflow (DescribeService → DescribeServiceEvent → DescribeServiceLog multi-keyword → ListServiceInstances → ListServiceContainers → DescribeServiceDiagnosis) on a chosen service. NEVER stop after listing.
2. Always finish with an analysis section. Every diagnosis MUST end with a written health-analysis + recommendation section. If the user described a symptom (e.g. "CUDA out of memory") that the live data does NOT show, you MUST still add a secondary section explaining common causes and fixes for that described symptom. Never end the turn with only raw command output.