CI: Geo-Spatial Plugin integration test

[andy-k-improving]

Description

This is a PR which aim to introduce a new IT test to assert and make sure the existing project setup and logic will work when Geo-Spatial installed within the same cluster.

High-level code changes include:

• Update Gradle file to download Geo-Spatial plugin for Integration test.
• Add an new test-case to perform assertion during PPL Integ-test time to make sure Plugin is available, the actual tests against GeoIp functionality will be added in sub-sequent PR along with the business logic.

Test-plan:

• Integ-testIT passed

Related Issues

Resolves: #3037

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[LantaoJin]

Could you update the code base and re-run the CI workflows again?

[andy-k-improving]

Checked the log from CI build, it's blocked by #3235.

[andy-k-improving]

@LantaoJin All tests are passing except bwc, can you have another look?
Thanks!

[penghuo]

Is there a specific reason for separating integTestWithGeo from integTest?

[andy-k-improving]

integTestWithGeo got separated as it requires an additional plugin Geo-spatial, by having a separate build target with external deps will help troubleshot in the case of build failure.
Similar to the existing build target: integTestWithSecurity.

[penghuo]

by having a separate build target with external deps will help troubleshot in the case of build failure.

could u elberate more on this. i think integTest already have clear hint on failed test cases.

If Geo command/function is native PPL feature, and OpenSearch release by defalut included geo-spatial plugin It not necessary to sepreate it from integTest. The geo-spatial use case is more similar to job-scheduler, instead of security plugin.

[andy-k-improving]

@penghuo Thanks for your comment, actually you do have the point on this, especially geo-spatial being packaged with OpenSearch release.
If that is the case, I will remove this CI and move the test-case back to ppl package.

[andy-k-improving]

I have updated the code to reflect above, @penghuo can you have another look?
Thanks!

[acarbonetto]

LGTM

[andy-k-improving]

@YANG-DB

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/sql/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/sql/backport-2.x
# Create a new branch
git switch --create backport/backport-3244-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ef3d7b6606285daa4de86f793a6647b93e6a9000
# Push it to GitHub
git push --set-upstream origin backport/backport-3244-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/sql/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-3244-to-2.x.