Viridian -> Cloud rename in hz-docs Pt1 (#1017)

These files can be backported

antora-playbook-local.yml

@@ -30,7 +30,7 @@ asciidoc:
     idseparator: '-'
     # Variables used in the docs
     page-survey: https://www.surveymonkey.co.uk/r/NYGJNF9
-    hazelcast-cloud: Viridian Cloud
+    hazelcast-cloud: Cloud
     ucn: User Code Namespaces
     ucd: User Code Deployment
   extensions:

antora-playbook.yml

@@ -27,7 +27,7 @@ asciidoc:
     idseparator: '-'
     # Variables used in the docs
     page-survey: https://www.surveymonkey.co.uk/r/NYGJNF9
-    hazelcast-cloud: Viridian Cloud
+    hazelcast-cloud: Cloud
     ucn: User Code Namespaces
     ucd: User Code Deployment
   extensions:

check-links-playbook.yml

@@ -21,7 +21,7 @@ content:
   - url: https://github.com/hazelcast/hazelcast-platform-operator-docs
     branches: [main]
     start_path: docs
-  - url: https://github.com/hazelcast-guides/sql_basics_on_viridian
+  - url: https://github.com/hazelcast-guides/sql_basics_on_cloud
     branches: master
     start_paths: docs
   - url: https://github.com/hazelcast-guides/client-failover

docs/modules/deploy/pages/choosing-a-deployment-option.adoc

@@ -1,7 +1,7 @@
 = Choosing an Application Topology
 :description: Hazelcast offers two topologies to use Hazelcast: embedded in a Java application or in a client/server topology. To help you choose a topology that meets your requirements, this topic describes each option.
 :page-aliases: ROOT:topologies.adoc
-:url-cloud-signup: https://viridian.hazelcast.com/sign-in?next=/
+:url-cloud-signup: https://cloud.hazelcast.com/sign-in?next=/
 
 You can deploy Hazelcast in two topologies, depending on where you want the Hazelcast members to run: