Add release notes for v9.2.0 release (#136792)

Author: elasticsearchmachine

docs/release-notes/breaking-changes.md

@@ -12,14 +12,28 @@ If you are migrating from a version prior to version 9.0, you must first upgrade
 
 % ## Next version [elasticsearch-nextversion-breaking-changes]
 
-## 9.1.5 [elasticsearch-9.1.5-breaking-changes]
+## 9.2.0 [elasticsearch-9.2.0-breaking-changes]
+```{applies_to}
+stack: ga 9.2.0
+```
 
-There are no breaking changes associated with this release.
+Ingest Node:
+* Simulate API: Return 400 on invalid processor(s) [#130325](https://github.com/elastic/elasticsearch/pull/130325) (issue: [#120731](https://github.com/elastic/elasticsearch/issues/120731))
+
+Mapping:
+* Don't enable norms for fields of type text when the index mode is LogsDB or TSDB [#131317](https://github.com/elastic/elasticsearch/pull/131317)
+
+Vector Search:
+* Enable `exclude_source_vectors` by default for new indices [#131907](https://github.com/elastic/elasticsearch/pull/131907)
 
 ## 9.0.8 [elasticsearch-9.0.8-breaking-changes]
 
 There are no breaking changes associated with this release.
 
+## 9.1.5 [elasticsearch-9.1.5-breaking-changes]
+
+There are no breaking changes associated with this release.
+
 ## 9.1.4 [elasticsearch-9.1.4-breaking-changes]
 
 There are no breaking changes associated with this release.

docs/release-notes/changelog-bundles/9.1.5.yml

@@ -74,10 +74,11 @@ changelogs:
       body: |-
         Queries using LIMIT followed by MV_EXPAND before a remote ENRICH can produce incorrect results due to distributed execution semantics.
         These queries are now unsupported and produce an error. Example:
-        [source,yaml]
-        ----------------------------
+        
+        ```yaml
         FROM *:events | SORT @timestamp | LIMIT 2 | MV_EXPAND ip | ENRICH _remote:clientip_policy ON ip
-        ----------------------------
+        ```
+        
         To avoid this error, reorder your query, for example by moving ENRICH earlier in the pipeline.
       pr: 135051
   - pr: 135078