fix(opensearch): Use the Maven repository of OpenSearch instead of Sonatype

[siegfriedweber]

Description

The build of OpenSearch 3.1.0 failed with the following error:

A problem occurred configuring root project 'opensearch-security'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not resolve org.opensearch.gradle:build-tools:3.1.0-SNAPSHOT.
     Required by:
         root project :
      > Could not resolve org.opensearch.gradle:build-tools:3.1.0-SNAPSHOT.
         > Unable to load Maven meta-data from https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/gradle/build-tools/3.1.0-SNAPSHOT/maven-metadata.xml.
            > Could not GET 'https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/gradle/build-tools/3.1.0-SNAPSHOT/maven-metadata.xml'. Received status code 402 from server: Payment Required
      > Could not resolve org.opensearch.gradle:build-tools:3.1.0-SNAPSHOT.
         > Unable to load Maven meta-data from https://artifacts.opensearch.org/snapshots/lucene/org/opensearch/gradle/build-tools/3.1.0-SNAPSHOT/maven-metadata.xml.
            > Could not GET 'https://artifacts.opensearch.org/snapshots/lucene/org/opensearch/gradle/build-tools/3.1.0-SNAPSHOT/maven-metadata.xml'. Received status code 403 from server: Forbidden

The OpenSearch Security Plugin 3.1.0.0 uses SNAPSHOT artifacts for the build. These artifacts are downloaded from Sonatype. Sonatype changed its policy to remove snapshot artifacts after 30 days which resulted in the error above. Therefore, in OpenSearch 3.4.0 the Sonatype Maven repository was replaced with the one from OpenSearch (opensearch-project/opensearch-build#5360). This change was backported to OpenSearch 3.3.0, but not to 3.1.0. This pull request backports opensearch-project/security#5711 and solves the issue.

Definition of Done Checklist

Note

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant.

Please make sure all these things are done and tick the boxes

• Changes are OpenShift compatible

TIP: Running integration tests with a new product image

The image can be built and uploaded to the kind cluster with the following commands:

boil build <IMAGE> --image-version <RELEASE_VERSION> --strip-architecture --load
kind load docker-image <MANIFEST_URI> --name=<name-of-your-test-cluster>

See the output of boil to retrieve the image manifest URI for <MANIFEST_URI>.