Align Enterprise troubleshooting skill with current support guidance

[rajshah4]

Desired Behavior

The OpenHands Enterprise troubleshooting skill aligns with current troubleshooting and VM log-collection documentation while keeping customer investigations read-only unless OpenHands Support explicitly directs a change.

Acceptance Criteria

• The official read-only Kubernetes warning is prominent.
• Troubleshooting and VM log-collection links are current.
• Failed-install and post-install support-bundle commands match current guidance.
• Mutation paths require explicit Support direction and administrator approval.
• Skill validation and repository tests pass.

Context

This tracks the documentation and safety alignment implemented by PR #457 on top of the skill introduced in PR #456.

This issue was updated by an AI agent (OpenHands) on behalf of Rajiv Shah.

[github-actions]

⚠️ Not yet ready-for-dev

This issue does not yet meet the readiness criteria, so the
ready-for-dev label has not been applied (or has been removed).
The criteria are type-specific:

Bug reports (bug label):

• The ### Actual Behavior section must describe reproducible steps
  and include a command such as uv run pytest, pytest, python,
  pip, npm run, or node.
• An ### Acceptance Criteria section with at least one checklist item (- [ ] ...).

Enhancements (enhancement label):

• A ### Desired Behavior section.
• An ### Acceptance Criteria section with at least one checklist item.

What is missing:

• The issue has neither the bug nor enhancement label, so its readiness criteria cannot be evaluated. Add the appropriate label.

Edit the issue to address the gaps and the ready-for-dev label will be
applied automatically.

This is an automated readiness check posted by a workflow.