### Description

Users may see the below log message under various circumstances,

> https://github.com/elastic/elasticsearch/blob/v8.3.3/server/src/main/java/org/elasticsearch/index/mapper/TextFieldMapper.java#L899-L906
> Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [FIELD_NAME] in order to load field data by uninverting the inverted index. Note that this can use significant memory.

as people seem to have mentioned this message in [Elasticsearch](https://github.com/elastic/elasticsearch/issues?q=is%3Aissue+%22Text+fields+are+not+optimised+for+operations%22+), [Kibana](https://github.com/elastic/kibana/issues?q=is%3Aissue+%22Text+fields+are+not+optimised+for+operations%22+), and [Beats](https://github.com/elastic/beats/issues?q=is%3Aissue+%22Text+fields+are+not+optimised+for+operations%22+) GH issues as well as at [forums](https://discuss.elastic.co/search?q=%22Text%20fields%20are%20not%20optimised%20for%20operations%22).

I don't intend to suggest revise of this well-known message but want to propose an insertion of contextual information - i.e. field and index name to clarify where to start troubleshooting at a glance.

**Proposal**

```diff
diff --git a/server/src/main/java/org/elasticsearch/index/mapper/TextFieldMapper.java b/server/src/main/java/org/elasticsearch/index/mapper/TextFieldMapper.java
index 045be484f09..74df90ffc0f 100644
--- a/server/src/main/java/org/elasticsearch/index/mapper/TextFieldMapper.java
+++ b/server/src/main/java/org/elasticsearch/index/mapper/TextFieldMapper.java
@@ -909,7 +909,8 @@ public class TextFieldMapper extends FieldMapper {
             } else if (operation == FielddataOperation.SEARCH) {
                 if (fielddata == false) {
                     throw new IllegalArgumentException(
-                        "Text fields are not optimised for operations that require per-document "
+                        "Field data is disabled on [" + name() + "] in [" + fieldDataContext.fullyQualifiedIndexName() + "]. "
+                            + "Text fields are not optimised for operations that require per-document "
                             + "field data like aggregations and sorting, so these operations are disabled by default. Please use a "
                             + "keyword field instead. Alternatively, set fielddata=true on ["
                             + name()
```

If this proposal sounds reasonable, please let me know, and I will open PRs accordingly. Thanks.
server/src/main/java/org/elasticsearch/index/mapper/TextFieldMapper.java
public static final String CONTENT_TYPE = "text";
    private static final String FAST_PHRASE_SUFFIX = "._index_phrase";
    private static final String FAST_PREFIX_SUFFIX = "._index_prefix";
    public static class Defaults {
        public static final double FIELDDATA_MIN_FREQUENCY = 0;
        public static final double FIELDDATA_MAX_FREQUENCY = Integer.MAX_VALUE;
        public static final int FIELDDATA_MIN_SEGMENT_SIZE = 0;
        public static final int INDEX_PREFIX_MIN_CHARS = 2;
        public static final int INDEX_PREFIX_MAX_CHARS = 5;
        public static final FieldType FIELD_TYPE = new FieldType();
        static {
            FIELD_TYPE.setTokenized(true);
            FIELD_TYPE.setStored(false);
            FIELD_TYPE.setStoreTermVectors(false);
            FIELD_TYPE.setOmitNorms(false);
            FIELD_TYPE.setIndexOptions(IndexOptions.DOCS_AND_FREQS_AND_POSITIONS);
            FIELD_TYPE.freeze();
        }
        /**
         * The default position_increment_gap is set to 100 so that phrase
         * queries of reasonably high slop will not match across field values.
         */
        public static final int POSITION_INCREMENT_GAP = 100;
    }
    private static final class PrefixConfig implements ToXContent {