[DOC] Clarify rolling upgrades of Kibana are not supported and report… (#117644) (#122797)

* [DOC] Clarify rolling upgrades of Kibana are not supported and reporting settings

I would like to clarify:
- rolling upgrades are not supported and highlight all Kibana instances must be stopped prior an upgrade
- cookie statement might be misleading
- https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html#reporting-kibana-server-settings reporting settings are missing

Please rephrase/reorganize the statements. A link to the reporting documentation would be useful.

* Update docs/user/production-considerations/production.asciidoc

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>

* Update docs/user/production-considerations/production.asciidoc

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>

* Update docs/user/production-considerations/production.asciidoc

* Update docs/user/production-considerations/production.asciidoc

* Update docs/user/production-considerations/production.asciidoc

* Update docs/user/production-considerations/production.asciidoc

* Update docs/user/production-considerations/production.asciidoc

* Update docs/user/production-considerations/production.asciidoc

* Update docs/user/production-considerations/production.asciidoc

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
(cherry picked from commit f7a970dbc2)

Co-authored-by: Luca Belluccini <luca.belluccini@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

docs/user/production-considerations/production.asciidoc

@@ -67,6 +67,11 @@ csp.strict: true
 
 See <<configuring-tls>>.
 
+[WARNING]
+====
+{kib} does not support rolling upgrades, and deploying mixed versions of {kib} can result in data loss or upgrade failures. Please shut down all instances of {kib} before performing an upgrade, and ensure all running {kib} instances have matching versions.
+====
+
 [float]
 [[load-balancing-kibana]]
 === Load balancing across multiple Kibana instances
@@ -109,13 +114,18 @@ bin/kibana -c config/instance2.yml
 === Accessing multiple load-balanced {kib} clusters
 
 To access multiple load-balanced {kib} clusters from the same browser,
-set `xpack.security.cookieName` in the configuration.
+explicitly set `xpack.security.cookieName` to the same value in the {kib} configuration
+of each {kib} instance.
+
+Each {kib} cluster must have a different value of `xpack.security.cookieName`.
+
 This avoids conflicts between cookies from the different {kib} instances.
 
-In each cluster, {kib} instances should have the same `cookieName`
-value. This will achieve seamless high availability and keep the session
+This will achieve seamless high availability and keep the session
 active in case of failure from the currently used instance.
 
+
+
 [float]
 [[high-availability]]
 === High availability across multiple {es} nodes