[Internal]: Documentation should emphasize how to differentiate text from semantic text and get inference fields

[kderusso]

Description

Today we document how to get inference fields for a semantic_text field here. We have determined that this is not sufficient and we need more/better documentation to emphasize this to users.

There is some work that is dependent on field caps features on our roadmap, but we should help our users the best we can even before that is available.

Resources

https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/semantic-text#troubleshooting-semantic-text-fields

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

No difference.

What release is this request related to?

N/A

Serverless release

Already live

Collaboration model

The documentation team

Point of contact.

Main contact: @Mikep86 @kderusso

Stakeholders: @liladler

[Mikep86]

I don't think we need to focus on the field caps text vs. semantic text issue in this docs update. AFAIK that is mostly an internal problem for Kibana & Security/O11y devs. External users can simply check the mappings. Given this documentation would be added to the semantic text mapping docs, it seems a bit redundant. We would basically be saying, "Here is documentation for the semantic text mapping. If you want to check if a field is a semantic text field, check the index mapping."