[k8s][vm] Refactor troubleshooting section

[a-velasco]

Our troubleshooting docs need a more opinionated structure so that the user understands where to get information about:

• general troubleshooting guidance ("I don't know what the problem is or how to find out")
• specific troubleshooting guidance ("I have this specific problem")
• tools (SoS report, Logs, observability...)

Improve landing page, make sure individual guides are correctly and clearly applied to both substrates, restructure as needed.

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-9498.

This message was autogenerated