Fix tags for Preferred data tier

[yetanothertw]

Summary

part of #4117

Replacing all the tags on the page with stack as it applies to all deployments. The tab titles were also wrong, they should be split as UI vs API instructions.

Generative AI disclosure

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

• Yes
• No

[github-actions]

Vale Linting Results

Summary: 2 suggestions found

💡 Suggestions (2)

File	Line	Rule	Message
troubleshoot/elasticsearch/add-tier.md	24	Elastic.Wordiness	Consider using 'to' instead of 'In order to'.
troubleshoot/elasticsearch/add-tier.md	68	Elastic.Wordiness	Consider using 'to' instead of 'In order to'.

[github-actions]

🔍 Preview links for changed docs

• troubleshoot/elasticsearch/add-tier.md

[shainaraskas]

tyty!

a stray thought: in my other PR, I have the tabs as Using {{kib}} / Using the {{es}} API. We don't have to align on this right now but we should figure out how to phrase this consistently in future.

we do have like a billion APIs, so specifying that you have to use the ES API for this is somewhat useful.

[yetanothertw]

a stray thought: in my other PR, I have the tabs as Using {{kib}} / Using the {{es}} API. We don't have to align on this right now but we should figure out how to phrase this consistently in future.

we do have like a billion APIs, so specifying that you have to use the ES API for this is somewhat useful.

That's a good point, we should align on it. I've noticed a lot of Kibana/API as tab headers in the Manage data section, so I just went with it instinctively since it's the shortest (easiest to read) option.
(We would often link to the API docs for the particular API we would be using, so the API could be inferred from that.)

[yetanothertw]

I can change that to Using {{kib}} / Using the {{es}} API in #4465