Fix dead links (#1389)

The test developed in #1382
flagged multiple dead links.

This PR fixes those _seperately_ to prove the status of the test.

Note the changes from `install-hazelcast.adoc` ~~copy from~~ overlap
with #1355.

docs/modules/data-structures/pages/fencedlock.adoc

@@ -51,7 +51,7 @@ image:ROOT:FencedLock.png[Fenced Lock]
 
 You can read more about the fencing token idea in Martin Kleppmann's
 https://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html[How to do distributed locking]
-blog post and Google's https://ai.google/research/pubs/pub27897[Chubby paper].
+blog post and Google's https://static.googleusercontent.com/media/research.google.com/en//archive/chubby-osdi06.pdf[Chubby paper].
 `FencedLock` integrates this idea with the `j.u.c.locks.Lock` abstraction,
 excluding `j.u.c.locks.Condition`. `newCondition()` is not implemented and
 throws `UnsupportedOperationException`.
@@ -112,4 +112,4 @@ dead member will be removed so that those
 locks are immediately available for live members.
 * Locks are re-entrant. The same thread can lock multiple times on the same lock.
 Note that for other threads to be able to require this lock, the owner of the lock
-must call `unlock` as many times as the owner called `lock`.
+must call `unlock` as many times as the owner called `lock`.

docs/modules/deploy/pages/deploying-on-azure.adoc

@@ -307,4 +307,4 @@ config.getPartitionGroupConfig()
 
 == Automated Deployment
 
-You can also use the https://github.com/Azure/azure-quickstart-templates/tree/master/hazelcast-vm-cluster[Azure Hazelcast Template] to automatically deploy a Hazelcast cluster.
+You can also use the https://github.com/Azure/azure-quickstart-templates/blob/master/application-workloads/hazelcase/hazelcast-vm-cluster/README.md[Azure Hazelcast Template] to automatically deploy a Hazelcast cluster.

docs/modules/getting-started/pages/install-enterprise.adoc

@@ -60,7 +60,7 @@ Windows::
 +
 --
 ifdef::snapshot[]
-Download and extract the link:https://repository.hazelcast.com/snapshot/com/hazelcast/hazelcast-enterprise/hazelcast-enterprise-{full-version}.zip[Hazelcast ZIP file].
+Download and extract the Hazelcast ZIP file from link:https://hazelcast.jfrog.io/ui/native/snapshot/com/hazelcast/hazelcast-enterprise-distribution/{full-version}[the repository].
 endif::[]
 ifndef::snapshot[]
 Download and extract the link:https://repository.hazelcast.com/download/hazelcast-enterprise/hazelcast-enterprise-{full-version}.zip[Hazelcast ZIP file].

docs/modules/getting-started/pages/install-hazelcast.adoc

@@ -135,13 +135,8 @@ Mac::
 Linux:: 
 + 
 --
-ifdef::snapshot[]
-Go to the link:https://oss.sonatype.org/content/repositories/snapshots/com/hazelcast/hazelcast-distribution/{full-version}/[snapshot repository] and click the download link for the TAR file that has the most up-to-date timestamp in the *Last Modified* columns.
-endif::[]
-ifndef::snapshot[]
 . Download a package from https://hazelcast.com/get-started/download/?utm_source=docs-website[hazelcast.com^].
 . Extract the downloaded package.
-endif::[]
 --
 Windows:: 
 +
@@ -200,7 +195,10 @@ The Java package includes both a member API and a Java client API. The member AP
 If you aren't using a build tool:
 
 ifdef::snapshot[]
-* link:https://oss.sonatype.org/content/repositories/snapshots/com/hazelcast/hazelcast/{last-oss-version}/[download the Hazelcast JAR file]
+* link:https://repo1.maven.org/maven2/com/hazelcast/hazelcast/{last-oss-version}/hazelcast-{last-oss-version}/[download the Hazelcast JAR file]
+endif::[]
+ifndef::snapshot[]
+* link:https://repo1.maven.org/maven2/com/hazelcast/hazelcast/{full-version}/hazelcast-{full-version}.jar[download the Hazelcast JAR file]
 endif::[]
 * add it to your classpath.
 

docs/modules/integrate/pages/cdc-connectors.adoc

@@ -62,12 +62,12 @@ PostgreSQL-specific connector:
 
 The Java API supports the following types of CDC source:
 
-* link:https://docs.hazelcast.org/docs/{full-version}/javadoc/com/hazelcast/enterprise/jet/cdc/DebeziumCdcSources.html[DebeziumCdcSources, window=_blank]:
+* link:https://docs.hazelcast.org/hazelcast-ee-docs/{full-version}/javadoc/com/hazelcast/enterprise/jet/cdc/DebeziumCdcSources.html[DebeziumCdcSources, window=_blank]:
   a generic source for all databases supported by Debezium
-* link:https://docs.hazelcast.org/docs/{full-version}/javadoc/com/hazelcast/enterprise/jet/cdc/mysql/MySqlCdcSources.html[MySqlCdcSources, window=_blank]:
+* link:https://docs.hazelcast.org/hazelcast-ee-docs/{full-version}/javadoc/com/hazelcast/enterprise/jet/cdc/mysql/MySqlCdcSources.html[MySqlCdcSources, window=_blank]:
   a specific, first class Jet CDC source for MySQL databases (also based
   on Debezium, but with the additional benefits provided by Hazelcast)
-* link:https://docs.hazelcast.org/docs/{full-version}/javadoc/com/hazelcast/enterprise/jet/cdc/postgres/PostgresCdcSources.html[PostgresCdcSources, window=_blank]:
+* link:https://docs.hazelcast.org/hazelcast-ee-docs/{full-version}/javadoc/com/hazelcast/enterprise/jet/cdc/postgres/PostgresCdcSources.html[PostgresCdcSources, window=_blank]:
   a specific, first class CDC source for PostgreSQL databases (also based
 on Debezium, but with the additional benefits provided by Hazelcast)
 

docs/modules/maintain-cluster/pages/rolling-upgrades.adoc

@@ -15,7 +15,7 @@ Before starting a rolling upgrade, consider the following best practices:
 * Ensure that <<hazelcast-members-compatibility,Upgrade Compatibility>> covers your requirements
 * If the minimum version of JDK has changed between releases, <<updated-jdk,upgrade the JDK version>> before starting a rolling upgrade
 * If you used Hazelcast Operator to deploy your cluster, refer to the link:https://docs.hazelcast.com/operator/latest/scaling-upgrading#upgrading[Operator documentation, window=_blank]
-* If using Hazelcast Management Center to trigger your rolling upgrade, upgrade Management Center before upgrading your members. For information on upgrading Management Center, refer to the link:https://docs.hazelcast.com/management-center/latest/getting-started/install[Management Center documentation, window=_blank], or if you deployed Management Center using the Hazelcast Operator, refer to the link:https://docs.hazelcast.com/operator/latest/deploy-management-center.adoc[Operator documentation, window=_blank]
+* If using Hazelcast Management Center to trigger your rolling upgrade, upgrade Management Center before upgrading your members. For information on upgrading Management Center, refer to the link:https://docs.hazelcast.com/management-center/latest/getting-started/install[Management Center documentation, window=_blank], or if you deployed Management Center using the Hazelcast Operator, refer to the link:https://docs.hazelcast.com/operator/latest/deploy-management-center[Operator documentation, window=_blank]
 * If using the `hz-cluster-admin` script to update your cluster, enable the `CLUSTER_WRITE` endpoints in the REST API. For further information on the {open-source-product-name} REST API, see xref:maintain-cluster:rest-api.adoc#using-the-rest-endpoint-groups[{open-source-product-name} REST API]. For further information on the {enterprise-product-name} REST API, see xref:maintain-cluster:enterprise-rest-api.adoc#dynamic-configuration-update-rest-endpoint[{enterprise-product-name} REST API]
 * Plan sufficient time for the migration and upgrade to complete, and remember that the members cannot change during the upgrade
 * Avoid issues where an automatic upgrade is triggered before the last member has been upgraded by setting a <<enabling-auto-upgrading,minimum cluster size>>

docs/modules/pipelines/pages/cdc.adoc

@@ -152,8 +152,13 @@ mysql> SELECT * FROM customers;
 +
 If you already have Hazelcast and you skipped the above steps, make sure to
 follow from here on.
-
-. Make sure the MySQL CDC plugin is in the `lib/` directory. You must manually download the MySQL CDC plugin from link:https://repo1.maven.org/maven2/com/hazelcast/jet/hazelcast-enterprise-cdc-mysql/{full-version}/hazelcast-enterprise-cdc-mysql-{full-version}-jar-with-dependencies.jar[Hazelcast's Maven repository, window=_blank] and then copy it to the `lib/` directory.
+ifdef::snapshot[]
+Download and extract the link:https://repository.hazelcast.com/snapshot/com/hazelcast/hazelcast-enterprise/hazelcast-enterprise-{full-version}.zip[Hazelcast ZIP file].
+. Make sure the MySQL CDC plugin is in the `lib/` directory. You must manually download the MySQL CDC plugin's `jar-with-dependencies` from link:https://hazelcast.jfrog.io/artifactory/snapshot/com/hazelcast/jet/hazelcast-enterprise-cdc-mysql/{full-version}[Hazelcast's Maven repository, window=_blank] and then copy it to the `lib/` directory.
+endif::[]
+ifndef::snapshot[]
+. Make sure the MySQL CDC plugin is in the `lib/` directory. You must manually download the MySQL CDC plugin from link:https://hazelcast.jfrog.io/artifactory/release/com/hazelcast/jet/hazelcast-enterprise-cdc-mysql/{full-version}/hazelcast-enterprise-cdc-mysql-{full-version}-jar-with-dependencies.jar[Hazelcast's Maven repository, window=_blank] and then copy it to the `lib/` directory.
+endif::[]
 +
 [source,bash]
 ----

docs/modules/pipelines/pages/spring-boot.adoc

@@ -3,7 +3,7 @@
 Spring Boot makes it easy to create and use third-party libraries, such
 as Hazelcast, with minimum configurations possible. While Spring
 Boot provides starters for some libraries, Hazelcast hosts its own
-link:https://github.com/hazelcast/hazelcast-jet-contrib/tree/master/hazelcast-jet-spring-boot-starter[starter].
+link:https://github.com/hazelcast/hazelcast-jet-contrib/tree/jet-4.5-maintenance/hazelcast-jet-spring-boot-starter[starter].
 
 Let's create a simple Spring Boot application which starts a Hazelcast
 member and auto-wires it.

docs/modules/pipelines/pages/submitting-jobs.adoc

@@ -262,7 +262,7 @@ To build an uber JAR, there are several options:
 
 * link:https://maven.apache.org/plugins/maven-assembly-plugin[Maven Assembly Plugin]
 * link:https://maven.apache.org/plugins/maven-shade-plugin[Maven Shade Plugin]
-* link:https://imperceptiblethoughts.com/shadow/introduction[Gradle Shadow Plugin].
+* link:https://gradleup.com/shadow/introduction[Gradle Shadow Plugin].
 
 === Adding to Member Classpaths
 

docs/modules/release-notes/pages/5-3-0.adoc

@@ -121,7 +121,7 @@ https://github.com/hazelcast/hazelcast/pull/24356[#24356]
 * Added compound identifier for the `externalName()` method.
 https://github.com/hazelcast/hazelcast/pull/23772[#23772]
 * Added an option for the MongoDB source to perform reading with a single processor instance. Usually distributing the operations is the best practice; however,
-the `$function` aggregation method is not supported by the Atlas Serverless instances. In this case, this newly introduced option can be used to query such instances in one processor. See the option's https://github.com/hazelcast/hazelcast/blob/master/hazelcast-sql/src/main/java/com/hazelcast/jet/sql/impl/connector/mongodb/Options.java#L77[documentation].
+the `$function` aggregation method is not supported by the Atlas Serverless instances. In this case, this newly introduced option can be used to query such instances in one processor. See the option's https://github.com/hazelcast/hazelcast/blob/v5.3.0/hazelcast-sql/src/main/java/com/hazelcast/jet/sql/impl/connector/mongodb/Options.java#72[documentation].
 https://github.com/hazelcast/hazelcast/pull/24198/files[#24198]
 * Added additional permission checks to JDBC connectors (source and sink). The previous checks in some cases used only the `jdbc:` name in `ConnectorPermission`.
 The newly introduced checks get the JDBC URL from existing connection metadata and check if the permission is granted. If you want to grant a `ConnectorPermission`