DOC-300: update client and tool compatibility [v/5.6] (#2082)

Backport of #2056

Update the content and presentation of client and tool versions. General
update and reorganize.

Preview:
https://deploy-preview-2056--hardcore-allen-f5257d.netlify.app/hazelcast/5.7-snapshot/deploy/versioning-compatibility#clients-and-tools

Co-authored-by: Rob Swain <rob.swain@hazelcast.com>

Author: github-actions[bot]

docs/modules/deploy/pages/versioning-compatibility.adoc

@@ -1,35 +1,11 @@
-= Supported Versions and Compatibilities 
-:description: This section provides the supported versions and interoperability of Hazelcast Platform and its modules.
+= Supported versions
+:description: Hazelcast Platform can be deployed in a wide range of environments with multiple clients and other components. It is important to ensure you use compatible versions for each part of your Hazelcast deployment.
 :page-aliases: deploy:supported-jvms.adoc
 :page-icons: font
 
 {description}
 
-== Semantic Versioning
-
-Hazelcast Platform uses https://semver.org/[semantic versioning] where versions appear in the following format:
-
-`major.minor.patch`
-
-For example, in Platform version 5.2.1, *5* is the major version, *2* is the minor version, and *1* is the patch version.
-
-Semantic versioning separates new releases into three types:
-
-* Major: This version may include  breaking changes.
-* Minor: This version includes backward-compatible functionality.
-* Patch: This version includes backward-compatible bug fixes.
-
-=== API Compatibility Exceptions
-
-According to semantic versioning, a Platform job written using the Pipeline API in a previous minor version should compile and have the same behavior in later minor versions.
-
-However, note the following exceptions:
-
-* Classes in the `com.hazelcast.jet.core` package provide only patch-level compatibility guarantees.
-* Types and methods annotated with `@EvolvingApi` and `@Beta` provide only patch-level compatibility guarantee. These are typically new features where the API is subject to further changes.
-* Types and methods annotated with `@PrivateApi`, and classes in the `impl` and `internal` packages do not provide any compatibility guarantees between versions. These APIs are not meant for public use.
-
-== Supported Architectures
+== Architectures
 
 Hazelcast Platform has been tested on the following system architectures.
 
@@ -42,16 +18,13 @@ Hazelcast Platform has been tested on the following system architectures.
 |AArch64/ARM64
 |From Platform 5.3
 
-
 |===
 
-== Supported Operating Systems
+== Operating systems
 
-Hazelcast Platform has been tested against the following operating systems. It may run on others which are not listed here.
+Hazelcast Platform has been tested on the following operating systems. It may run on others that are not listed here.
 
 // tag::supported-os[]
-[options="header"]
-.Supported Operating Systems
 |===
 |OS | Platform {full-version}
 
@@ -73,20 +46,21 @@ Hazelcast Platform has been tested against the following operating systems. It m
 |Windows Server 2019
 |✓
 
-|Windows 10, 11footnote:dev[Suitable for the development of applications (or Hazelcast itself), _but not_ for production. Some features are not available or are not supported.]
-|Supported for development
+|Windows 10, 11
+|Supported for development only
 
-|macOSfootnote:dev[]
-|Supported for development
+|macOS
+|Supported for development only
 
 |===
 // end::supported-os[]
 
-== Supported Virtualization Environments
+NOTE: Windows 10 and 11 and macOS are not suitable for production. Some features are not available or are not supported.
+
+== Virtualization environments
 
-Hazelcast Platform has been tested against the following virtualization environments. It may run on others which are not listed here.
+Hazelcast Platform has been tested in the following virtualization environments. It may run on others that are not listed here.
 
-.Supported Virtualization Environments
 |===
 |Environment | Platform {full-version}
 
@@ -104,9 +78,10 @@ Hazelcast Platform has been tested against the following virtualization environm
 
 |===
 
-== Supported Public Cloud Environments
+== Public cloud environments
+
+Hazelcast Platform has been tested in the following public cloud environments. It may run on others that are not listed here.
 
-.Supported Cloud Environments
 |===
 |Environment | Platform {full-version}
 
@@ -124,14 +99,11 @@ Hazelcast Platform has been tested against the following virtualization environm
 
 |===
 
+== Java Development Kits (JDKs)
 
-== Supported Java Virtual Machines
-
-Hazelcast Platform runs on Java, and supports the following LTS JDKs. It may run on other JDK distributions which are not listed here.
+Hazelcast Platform runs on Java, and supports the following LTS JDKs. It may run on other JDK distributions that are not listed here.
 
 // tag::supported-jvms[]
-[options="header"]
-.Supported JDKs
 |===
 |JDK | Platform {full-version}
 
@@ -162,9 +134,87 @@ Hazelcast Platform runs on Java, and supports the following LTS JDKs. It may run
 |===
 // end::supported-jvms[]
 
-== Compatibility Guarantees
+== Clients and tools
+
+The following table shows compatibility between this version of Hazelcast Platform and Hazelcast administrative tools.
+
+|===
+|Tool |Minimum version |Recommended version
+
+|Management Center
+|5.5
+|{page-latest-supported-mc}
+
+|Operator
+|5.13
+|{page-latest-supported-po}
+
+|CLC
+|5.2.0
+|{page-latest-supported-clc}
+
+|===
+
+The following table shows compatibility between this version of Hazelcast Platform and all official clients.
+
+|===
+|Client |Minimum version |Recommended version
+
+|Java
+|Platform version
+|Platform version
+
+|.NET
+|4.0.0
+|{page-latest-supported-csharp-client}
 
-=== Cluster Members
+|C++
+|5.3.1
+|{page-latest-supported-cplusplus-client}
+
+|Python
+|4.0.0
+|{page-latest-supported-python-client}
+
+|Node.js
+|4.0.0
+|{page-latest-supported-nodejs-client}
+
+|Go
+|1.0.0
+|{page-latest-supported-go-client}
+
+|===
+
+NOTE: The Java client JAR is provided in the Hazelcast Platform package and has the same version number. Other clients are released separately.
+
+== Versioning and compatibility guarantees
+
+Hazelcast Platform uses https://semver.org/[semantic versioning], where versions appear in the following format:
+
+`major.minor.patch`
+
+For example, in Platform version 5.2.1, *5* is the major version, *2* is the minor version, and *1* is the patch version.
+
+This also defines three types of release, with differing levels of backward compatibility:
+
+* Major: This version may include breaking changes.
+* Minor: This version includes backward-compatible functionality.
+* Patch: This version includes backward-compatible bug fixes.
+
+In addition, Hazelcast offers several compatibility guarantees to ensure a predictable upgrade path for your deployment.
+
+=== APIs
+
+According to semantic versioning, a Platform job written using the Pipeline API in a previous minor version should compile and have the same behavior in later minor versions.
+
+However, note the following exceptions:
+
+* Classes in the `com.hazelcast.jet.core` package provide only patch-level compatibility guarantees.
+* Types and methods annotated with `@EvolvingApi` and `@Beta` provide only patch-level compatibility guarantee. These are typically new features where the API is subject to further changes.
+* Types and methods annotated with `@PrivateApi`, and classes in the `impl` and `internal` packages do not provide any compatibility guarantees between versions. These APIs are not meant for public use.
+
+=== Members
 
 Hazelcast Platform members operating on the same major and minor Platform version are always compatible, regardless of the patch version.
 
@@ -174,129 +224,23 @@ Each minor version is always compatible with the previous minor version.
 
 All 5.x.y versions of Management Center are compatible with Hazelcast Platform 5.x.y versions. We recommend you use a version of Management Center at least as high as the Hazelcast Platform version in your cluster. For example, Management Center 5.1.1 may not support all the features of Hazelcast Platform 5.2, or vice versa. You should generally upgrade to the latest version of Management Center when available and refer to xref:{page-latest-supported-mc}@management-center:release-notes:releases.adoc[Management Center release notes] for details on each version.
 
-=== Job States
+=== Job states
 
 Hazelcast Platform job states are only backward-compatible across the same minor versions.  A newer patch version is able to understand the job states only from the previous patch versions of the same minor version.
 
 If you have a running job, using the rolling upgrades feature, you are able to upgrade the cluster to a newer patch version without losing the state of a running job. See xref:maintain-cluster:rolling-upgrades.adoc[Rolling Upgrades]. Also note that jobs must be resubmitted after a rolling upgrade to a newer minor version since they don't run during upgrades. See xref:pipelines:submitting-jobs.adoc[Submitting Jobs].
 
 Hazelcast clients that submit jobs (currently only Java clients) are compatible with members running on the same minor version. This means that a client using an older or newer patch version is able to connect and submit a job to a cluster that's running a different patch version.
 
-=== Command Line Tools
+=== Command line tools
 
 Hazelcast xref:management:cluster-utilities.adoc#hazelcast-command-line-tool[CLI] and xref:management:cluster-utilities.adoc#using-the-hz-cluster-admin-script[cluster admin] tools are backwards-compatible across the same minor versions.
 
-=== Configuration Files
+=== Configuration files
 
 XML and YAML configuration files provided with the Hazelcast Platform package are backward-compatible across the same minor versions. After upgrading a cluster to a new minor version, the configuration files for the previous version can be used without any modification.
 
-=== Names of Metrics
+=== Metrics
 
 Hazelcast Platform sends metrics to Management Center and other means such as JMX. The names of these metrics may change across minor versions but not between patch versions.
 
-=== Client Version Compatibilities
-
-Hazelcast Platform has clients implemented in the following languages:
-
-* Java
-* {cpp}
-* .NET
-* Python
-* Go
-* Node.js
-* Hazelcast Command Line Client (CLC)
-
-The following table lists the compatibilities between client and Platform/IMDG versions.
-
-[cols="1,2a",options="header"]
-.Client Version Compatibilities
-|===
-|Client | Platform and/or IMDG
-
-|Java 5.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|Java 4.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|Java 3.6.x through 3.12.x
-|
-* IMDG 3.6.x through 3.12.x
-
-|{cpp} 5.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|{cpp} 4.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|{cpp} 3.6.x through 3.12.x
-|
-* IMDG 3.6.x through 3.12.x
-
-|.NET 5.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|.NET 4.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|.NET 3.6.x through 3.12.x
-|
-* IMDG 3.6.x through 3.12.x
-
-|Python 5.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|Python 4.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|Python 3.6.x through 3.12.x
-|
-* IMDG 3.6.x through 3.12.x
-
-|Node.js 5.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|Node.js 4.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|Node.js 3.6.x through 3.12.x
-|
-* IMDG 3.6.x through 3.12.x
-
-|Go 1.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|Go 0.x.y
-|
-* IMDG 3.6.x through 3.12.x
-
-|CLC 5.x.y
-|
-* Platform 5.x.y
-* IMDG 4.x.y
-
-|===
-
-