Extend context-aware documentation links to support other flavors

[dedemorton]

Describe the feature:

Relates to the kbn-doc-links service, implemented in #123818

In #167088, we added the ability to add context-aware documentation links for serverless.

We have a few instances where we would like to override the doc links to point to docs for a specific serverless solution. For example, in Observability serverless, the help link under the Dashboards UI should point to https://docs.elastic.co/serverless/observability/dashboards. In Elasticsearch serverless, it should point to https://docs.elastic.co/serverless/elasticsearch/explore-your-data-visualize-your-data. But because the UI is shared, we currently can't override the help link for each solution.

There is also an emerging requirement to override doc links when a UI appears in cloud, so we might need to extend the doc link service with additional "flavors". cc @florent-leborgne for more detail about this requirement.

Describe a specific use case for the feature:

Users accessing the documentation should be presented with the correct documentation for the solution they are using.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[dedemorton]

Looks like there is a request to add cloud-aware links here: #176997

[pgayvallet]

We have a few instances where we would like to override the doc links to point to docs for a specific serverless solution

If I do understand the need, this may require slightly more work than #167088, as technically the serverless project type is not really a concrete concept in Core at the moment.

[pgayvallet]

@dedemorton is that still something you would need?

[dedemorton]

@pgayvallet Good question. The answer is a little complicated. After we migrate our docs to docsmobile (aka "next docs"), we plan to remove duplicated content where possible, which means we might no long need the ability to override links at a solution level. However this plan is still a WIP. Since my team (Observability docs) only has a couple instances where we need to override the link, it's not a high priority for us right now.

@florent-leborgne What do you think?

[dedemorton]

Closing because this work will probably not be required given our evolving docs IA plans.