Backport to 5.5 of DOC-532: update Enterprise overview, editions and quickstarts (#1784)

Following Enterprise Content plan to clarify and improve Enterprise
positioning, benefits and onboarding:
- [x] Add Features & Benefits table to Enterprise Overview AKA Editions
- [x] Merge Get Started with Enterprise with Persist Map Entries
tutorial
- [ ] Refine and save tutorial template (separate PR)
- [x] Correct and improve other EE GS tutorials
- [x] Review and correct licensing / install info
- [x] Check and correct terminology
- [x] Apply Google Style Guide
- [x] Update screenshots
- [x] _Change license key to secret?_ Add tip and link to PO tutorial
Closes [1833](#1833),
[1836](#1836)

Author: oliverhowell

docs/modules/ROOT/nav.adoc

@@ -1,24 +1,34 @@
 .Get started
 * xref:whats-new.adoc[What's new in 5.5]
 * xref:what-is-hazelcast.adoc[What is Hazelcast Platform]
-* xref:ask-ai.adoc[]
-* xref:getting-started:editions.adoc[Available versions]
+* xref:getting-started:editions.adoc[Hazelcast editions]
+// Getting started
 * Start a local cluster
 ** xref:getting-started:get-started-docker.adoc[Docker]
 ** xref:getting-started:get-started-cli.adoc[CLI]
 ** xref:getting-started:get-started-binary.adoc[Binary]
-** xref:getting-started:get-started-java.adoc[Java Embedded]
-* xref:getting-started:enterprise-overview.adoc[Get started with Enterprise Edition]
-** xref:getting-started:persistence.adoc[]
-** xref:getting-started:authenticate-clients.adoc[]
-** xref:getting-started:wan.adoc[]
-** xref:getting-started:blue-green.adoc[]
+** xref:getting-started:get-started-java.adoc[Java embedded]
+// Enterprise
+* xref:getting-started:get-started-enterprise.adoc[Get started with Enterprise]
+** xref:getting-started:authenticate-client-tutorial.adoc[]
+** xref:getting-started:wan-replication-tutorial.adoc[Replicate map across WAN clusters]
+** xref:getting-started:deploy-blue-green-tutorial.adoc[]
+// Clients
+* xref:clients:hazelcast-clients.adoc[Get started with clients]
+** xref:clients:java-client-getting-started.adoc[Get started with Java]
+** xref:clients:csharp-client-getting-started.adoc[Get started with .NET]
+** xref:clients:python-client-getting-started.adoc[Get started with Python]
+** xref:clients:cpp-client-getting-started.adoc[Get started with {cpp}]
+** xref:clients:go-client-getting-started.adoc[Get started with Go]
+** xref:clients:nodejs-client-getting-started.adoc[Get started with Node.js]
+// SQL
 * Get started with SQL
 ** xref:sql:get-started-sql.adoc[]
 ** xref:sql:learn-sql.adoc[]
 ** xref:sql:get-started-sql-files.adoc[]
-* xref:clients:hazelcast-clients.adoc[Get started with a Hazelcast Client]
-* xref:getting-started:support.adoc[]
+// Support
+* xref:getting-started:support.adoc[Get support]
+* xref:ask-ai.adoc[]
 
 .Install and upgrade
 // Overview
@@ -167,6 +177,18 @@ include::cp-subsystem:partial$nav.adoc[]
 include::data-connections:partial$nav.adoc[]
 include::wan:partial$nav.adoc[]
 * xref:cluster-performance:thread-per-core-tpc.adoc[]
+// Synchronizing data across clusters
+* Synchronizing data across clusters
+** xref:getting-started:wan-replication-tutorial.adoc[WAN Replication Overview]
+** xref:wan:modes.adoc[]
+** xref:wan:quick-start.adoc[]
+** xref:wan:defining-wan-replication.adoc[]
+** xref:wan:configuring-for-map-and-cache.adoc[]
+** xref:wan:advanced-features.adoc[]
+** xref:wan:tuning.adoc[]
+** xref:wan:failures.adoc[]
+** xref:wan:rest-api.adoc[]
+// Extending Hazelcast
 * xref:extending-hazelcast:extending-hazelcast.adoc[]
 ** xref:extending-hazelcast:operationparker.adoc[]
 ** xref:extending-hazelcast:discovery-spi.adoc[]

docs/modules/ROOT/pages/ask-ai.adoc

@@ -1,5 +1,5 @@
 = Ask AI
-:description: Use our Ask AI feature to get instant answers to technical questions.
+:description: Use our Ask AI feature to get instant answers to technical questions and help troubleshoot problems.
 
 {description}
 

docs/modules/ROOT/pages/capacity-planning.adoc

@@ -37,7 +37,7 @@ or asynchronous xref:data-structures:backing-up-maps.adoc[backups]?
 required to accommodate the data, both existing and new. Usually an eviction mechanism keeps
 the map/cache size in check, but the eviction itself does not always clear the memory almost
 immediately. Therefore, the answers to this question gives a good insight.
-* Are you using multiple clusters (which may involve xref:wan:wan.adoc[WAN Replication])?
+* Are you using multiple clusters (which may involve xref:getting-started:wan-replication-tutorial.adoc[WAN Replication])?
 * What are the throughput and latency requirements?
 ** The answer should be about Hazelcast access, not the application throughput.
 For example, an application may plan for 10,000 user TPS but each user

docs/modules/ROOT/pages/index.adoc

@@ -75,7 +75,7 @@ Also, Hazelcast can be used as a cache for applications based on the Spring Fram
 shared data in real time.
 
 You can have multiple Hazelcast clusters at different locations in sync
-by replicating their state over WAN environments. See the xref:wan:wan.adoc[Synchronizing Data Across a WAN section].
+by replicating their state over WAN environments. See the xref:getting-started:wan-replication-tutorial.adoc[Synchronizing Data Across a WAN section].
 
 You can listen to the events happening in the cluster, on the data structures and clients so that
 you are notified when those events happen. See the xref:events:distributed-events.adoc[Distributed Events section].

docs/modules/ROOT/pages/what-is-hazelcast.adoc

@@ -75,7 +75,7 @@ Also, Hazelcast can be used as a cache for applications based on the Spring Fram
 shared data in real time.
 
 You can have multiple Hazelcast clusters at different locations in sync
-by replicating their state over WAN environments. See the xref:wan:wan.adoc[Synchronizing Data Across a WAN section].
+by replicating their state over WAN environments. See the xref:getting-started:wan-replication-tutorial.adoc[Synchronizing Data Across a WAN section].
 
 You can listen to the events happening in the cluster, on the data structures and clients so that
 you are notified when those events happen. See the xref:events:distributed-events.adoc[Distributed Events section].

docs/modules/architecture/pages/architecture.adoc

@@ -39,7 +39,7 @@ cooperatively diagnose the state and immediately take over the responsibility
 of the failed member. To determine if a member is unreachable or crashed, Hazelcast
 provides built-in xref:clusters:failure-detector-configuration.adoc[failure detectors].
 
-Hazelcast also provides replication over WAN for high availability. You can have deployments across multiple data centers using the xref:wan:wan.adoc[WAN replication] mechanism which offers protection against a data center or wider network failures.
+Hazelcast also provides replication over WAN for high availability. You can have deployments across multiple data centers using the xref:getting-started:wan-replication-tutorial.adoc[WAN replication] mechanism which offers protection against a data center or wider network failures.
 
 == AP/CP