Update applies_to Stack/Serverless/Deploy/Product render order

[bmorelli25]

Summary

• 🍷 Pairs with Add automatic applies_to version sorting #1726.
• Closes Implement multiple lifecycle state logic #1435.
• Closes https://github.com/elastic/docs-content-internal/issues/216.

applies_to badges are rendered in a predefined order. This PR reorders the applies_to badge rendering in ApplicableToComponent.cshtml to follow a more logical hierarchy. The new order prioritizes Stack, then Serverless, followed by deployment options, then specialized tools and agents.

Important

I might not have this order correct. I welcome any opinions on what the correct order is.

I did try putting Serverless first, but there are some edge-case sections like this one where Stack really gets buried if it comes after Serverless. Thoughts?

I also considered creating a configuration file for the badge ordering, but opted for keeping the hardcoded config as this ordering is unlikely to change often and in its current state doesn't require any runtime configuration lookup.

New Rendering Order

1. Stack

• Stack

2. Serverless

• Serverless (when all projects share same applicability)
• Serverless Elasticsearch
• Serverless Observability
• Serverless Security

3. Deployment

• ECH
• ECK
• ECE
• Self-Managed

4. ProductApplicability

• ECCTL
• Curator
• EDOT (alphabetical):
  • EDOT Android
  • EDOT CF AWS
  • EDOT Collector
  • EDOT .NET
  • EDOT iOS
  • EDOT Java
  • EDOT Node.js
  • EDOT PHP
  • EDOT Python
• APM Agents (alphabetical):
  • APM Agent Android
  • APM Agent .NET
  • APM Agent Go
  • APM Agent iOS
  • APM Agent Java
  • APM Agent Node.js
  • APM Agent PHP
  • APM Agent Python
  • APM Agent Ruby
  • APM Agent RUM

5. Product (generic)

• Generic product applicability (catch-all)

[github-actions]

🔍 Preview links for changed docs

• docs/contribute/cumulative-docs/guidelines.md
• docs/syntax/applies.md

[colleenmcginnis]

In the existing Documenting versions and deployment types page (which was absorbed into other pages in #1614), we stated that the order should "reflect organizational priorities". The examples provided were that serverless should come before stack and the deployment types should be in this order: serverless (?), ech, eck, ece, self-managed. I'm not sure who came up with that guidance initially or if we want to follow it.

[shainaraskas]

👋 that was me making stuff up (but based on the push to serverless, and the deprioritization of ECE)

I think stack can come before serverless given your concerns, but I'd put the deployent types in the following order:
ech, eck, ece,self

[bmorelli25]

Thanks for the feedback. Apologies for missing it. Updated based on your suggested order.

[Mpdreamz]

LGTM ty @bmorelli25