Applies tag cleanup pt 1 (mostly troubleshooting topics)

[shainaraskas]

Summary

part of #4117

Fixes applies information on several troubleshooting pages. Did the following additional labor:

• Restructured some tabbed content: some ECH/self tab splits were actually Kibana/ES API splits. Others were ECE+ECH/ECK+self splits
• Added some hints around applicability for "shoulder" docs (e.g. discovery is much more automated in ECE/ECH/ECK, but the docs are still helpful)
• Fixed some linting stuff

Applicability was determined based on supporting documentation (e.g. availability of snapshot/restore plugins) and accessibility of the troubleshooting paths provided. Will get a double-check probably from Edu on my gut feelings

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

Confirmed assumptions about troubleshooting applicability with chatgpt

[github-actions]

Vale Linting Results

Summary: 4 suggestions found

💡 Suggestions (4)

File	Line	Rule	Message
troubleshoot/elasticsearch/decrease-disk-usage-data-node.md	29	Elastic.Versions	Use 'and later' instead of 'and higher' when referring to versions.
troubleshoot/elasticsearch/diagnose-unassigned-shards.md	138	Elastic.WordChoice	Consider using 'cannot' instead of 'unable', unless the term is in the UI.
troubleshoot/elasticsearch/discovery-troubleshooting.md	17	Elastic.WordChoice	Consider using 'cannot' instead of 'unable', unless the term is in the UI.
troubleshoot/elasticsearch/discovery-troubleshooting.md	19	Elastic.WordChoice	Consider using 'cannot' instead of 'unable', unless the term is in the UI.

[github-actions]

🔍 Preview links for changed docs

• troubleshoot/elasticsearch/decrease-disk-usage-data-node.md
• troubleshoot/elasticsearch/diagnose-unassigned-shards.md
• troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md
• troubleshoot/elasticsearch/diagnosing-invalid-repositories.md
• troubleshoot/elasticsearch/diagnosing-unknown-repositories.md
• troubleshoot/elasticsearch/diagnostic.md
• troubleshoot/elasticsearch/discovery-troubleshooting.md
• troubleshoot/elasticsearch/elasticsearch-hadoop/elasticsearch-for-apache-hadoop.md
• troubleshoot/elasticsearch/failed-to-parse-field-of-type.md
• troubleshoot/elasticsearch/fix-common-cluster-issues.md

More links …

• troubleshoot/elasticsearch/fix-data-node-out-of-disk.md
• troubleshoot/elasticsearch/fix-master-node-out-of-disk.md
• troubleshoot/elasticsearch/fix-other-node-out-of-disk.md
• troubleshoot/elasticsearch/fix-watermark-errors.md

[shainaraskas]

@eedugon hoping you can do a gut check on my changes and see if you think I've recategorized any of these incorrectly

[eedugon]

Looks great!

I shared some comments that you can ignore if you feel unneeded. More over the comments that suggest changes on the troubleshooting procedure itself which might not be the objective of this PR :)

btw, are you planning to fix the applies tags of https://www.elastic.co/docs/troubleshoot/elasticsearch/troubleshooting-unstable-cluster and its siblings in a different PR?

I think those would also need to remove deployment types and keep stack only.