Remove match_only_text and pattern_text from text docs page

Author: parkertimmins

docs/reference/elasticsearch/mapping-reference/text.md

@@ -292,122 +292,3 @@ PUT my-index-000001
   }
 }
 ```
-
-
-## Match-only text field type [match-only-text-field-type]
-
-A variant of [`text`](#text-field-type) that trades scoring and efficiency of positional queries for space efficiency. This field effectively stores data the same way as a `text` field that only indexes documents (`index_options: docs`) and disables norms (`norms: false`). Term queries perform as fast if not faster as on `text` fields, however queries that need positions such as the [`match_phrase` query](/reference/query-languages/query-dsl/query-dsl-match-query-phrase.md) perform slower as they need to look at the `_source` document to verify whether a phrase matches. All queries return constant scores that are equal to 1.0.
-
-Analysis is not configurable: text is always analyzed with the [default analyzer](docs-content://manage-data/data-store/text-analysis/specify-an-analyzer.md#specify-index-time-default-analyzer) ([`standard`](/reference/text-analysis/analysis-standard-analyzer.md) by default).
-
-[span queries](/reference/query-languages/query-dsl/span-queries.md) are not supported with this field, use [interval queries](/reference/query-languages/query-dsl/query-dsl-intervals-query.md) instead, or the [`text`](#text-field-type) field type if you absolutely need span queries.
-
-Other than that, `match_only_text` supports the same queries as `text`. And like `text`, it does not support sorting and has only limited support for aggregations.
-
-```console
-PUT logs
-{
-  "mappings": {
-    "properties": {
-      "@timestamp": {
-        "type": "date"
-      },
-      "message": {
-        "type": "match_only_text"
-      }
-    }
-  }
-}
-```
-
-
-### Parameters for match-only text fields [match-only-text-params]
-
-The following mapping parameters are accepted:
-
-[`fields`](/reference/elasticsearch/mapping-reference/multi-fields.md)
-:   Multi-fields allow the same string value to be indexed in multiple ways for different purposes, such as one field for search and a multi-field for sorting and aggregations, or the same string value analyzed by different analyzers.
-
-[`meta`](/reference/elasticsearch/mapping-reference/mapping-field-meta.md)
-:   Metadata about the field.
-
-
-## Pattern text field type [pattern-text-field-type]
-```{applies_to}
-serverless: preview
-stack: preview 9.2
-```
-:::{note}
-This feature requires a [subscription](https://www.elastic.co/subscriptions).
-:::
-
-The `pattern_text` field type is a variant of [`text`](#text-field-type) with improved space efficiency for log data.
-Internally, it decomposes values into static parts that are likely to be shared among many values, and dynamic parts that tend to vary.
-The static parts usually come from the explanatory text of a log message, while the dynamic parts are the variables that were interpolated into the logs.
-This decomposition allows for improved compression on log-like data.
-
-We call the static portion of the value the `template`.
-Although the template cannot be accessed directly, a separate field called `<field_name>.template_id` is accessible.
-This field is a hash of the template and can be used to group similar values.
-
-Analysis is configurable but defaults to a delimiter-based analyzer.
-This analyzer applies a lowercase filter and then splits on whitespace and the following delimiters: `=`, `?`, `:`, `[`, `]`, `{`, `}`, `"`, `\`, `'`.
-
-### Limitations
-
-Unlike most mapping types, `pattern_text` does not support multiple values for a given field per document.
-If a document is created with multiple values for a pattern_text field, an error will be returned.
-
-[span queries](/reference/query-languages/query-dsl/span-queries.md) are not supported with this field, use [interval queries](/reference/query-languages/query-dsl/query-dsl-intervals-query.md) instead, or the [`text`](#text-field-type) field type if you absolutely need span queries.
-
-Like `text`, `pattern_text` does not support sorting and has only limited support for aggregations.
-
-### Phrase matching
-Pattern text supports an `index_options` parameter with valid values of `docs` and `positions`.
-The default value is `docs`, which makes `pattern_text` behave similarly to `match_only_text` for phrase queries.
-Specifically, positions are not stored, which reduces the index size at the cost of slowing down phrase queries.
-If `index_options` is set to `positions`, positions are stored and `pattern_text` will support fast phrase queries.
-In both cases, all queries return a constant score of 1.0.
-
-### Index sorting for improved compression
-The compression provided by `pattern_text` can be significantly improved if the index is sorted by the `template_id` field.
-For example, a typical approach would be to sort first by `message.template_id`, then by `@timestamp`, as shown in the following example.
-
-```console
-PUT logs
-{
-  "settings": {
-    "index": {
-      "sort.field": [ "message.template_id", "@timestamp" ],
-      "sort.order": [ "asc", "desc" ]
-    }
-  },
-  "mappings": {
-    "properties": {
-      "@timestamp": {
-        "type": "date"
-      },
-      "message": {
-        "type": "pattern_text"
-      }
-    }
-  }
-}
-```
-
-
-### Parameters for pattern text fields [pattern-text-params]
-
-The following mapping parameters are accepted:
-
-[`analyzer`](/reference/elasticsearch/mapping-reference/analyzer.md)
-:   The [analyzer](docs-content://manage-data/data-store/text-analysis.md) which should be used for the `pattern_text` field, both at index-time and at search-time (unless overridden by the  [`search_analyzer`](/reference/elasticsearch/mapping-reference/search-analyzer.md)).
-Supports a delimiter-based analyzer and the standard analyzer, as is used in `match_only_text` mappings.
-Defaults to the delimiter-based analyzer, which applies a lowercase filter and then splits on whitespace and the following delimiters: `=`, `?`, `:`, `[`, `]`, `{`, `}`, `"`, `\`, `'`.
-
-[`index_options`](/reference/elasticsearch/mapping-reference/index-options.md)
-:   What information should be stored in the index, for search and highlighting purposes. Valid values are `docs` and `positions`. Defaults to `docs`.
-
-[`meta`](/reference/elasticsearch/mapping-reference/mapping-field-meta.md)
-:   Metadata about the field.
-