test(integ-test): exclude with gates for analytics-engine and Prometheus suites from integTestRemote

[mengweieric]

Description

integTestRemote runs against an externally provided cluster (-Dtests.rest.cluster), so it can neither install plugins nor set node-level settings. Two groups of suites depend on one of those and are still selected by the task, so they fail during setup rather than being skipped.

Group	Gate	Suites	Why they cannot run here
analytics-engine	else branch on the existing analyticsEnabled gate	AnalyticsEngineCompatIT, AnalyticsEngineSecurityIT, AnalyticsEngineProfileIT	create composite (parquet-backed) indices and need the node settings opensearch.experimental.feature.pluggable.dataformat.enabled and ...transport.stream.enabled; each has a dedicated task whose testClusters block provisions that stack
Prometheus	if (windows || ignorePrometheus), copied from integTest	PrometheusDataSourceCommandsIT, ShowDataSourcesCommandIT, InformationSchemaCommandIT	need a running Prometheus instance to query metrics

Observed when running integTestRemote against a cluster without the analytics-engine stack:

• AnalyticsEngineSecurityIT — all 21 tests fail in setup, and the suite is by a wide margin the slowest in the run. Its setup polls the security configuration API 60 times at one-second intervals and only sets its initialized flag once the poll succeeds, so every test method repeats the full wait before failing.
• AnalyticsEngineProfileIT — its index.pluggable.dataformat index creation returns 400, which the test treats as "index already exists", so later tests report a misleading no such index 404.
• AnalyticsEngineCompatIT — skips cleanly; it already self-guards with a @Before probe of _cat/plugins ([Backport 3.7] Skip AnalyticsEngineCompatIT when analytics-engine plugin is absent #5511). It is listed so the analytics-engine group stays complete if that guard is ever removed.
• The Prometheus suites fail creating their datasource, then fail again during @After cleanup.

Change

Both groups stay gated, so default behaviour does not change. The else branch is only taken when analyticsEnabled is false, the Prometheus group is opt-in through the existing ignorePrometheus flag, and the dedicated :analyticsEngineCompatIT, :analyticsEngineSecurityIT and :analyticsEngineProfileIT tasks are untouched and continue to run all three suites against clusters that provision what they need.

The analytics-engine exclusions are gated rather than added to the class-file exclusion list below, so that all analytics-engine filtering for this task stays together with the existing route-divergence exclusions.

Not included: the security package

integTest also excludes org/opensearch/sql/security/**, on the grounds that those suites run in :integTestWithSecurity. That reasoning does not carry over here, and this PR deliberately leaves them in place.

integTestWithSecurity runs against its own configureSecurityPlugin() test cluster, so it does not cover the remote case. integTestRemote forwards https, user and password specifically so that it can be pointed at a secured cluster, and against an FGAC-enabled cluster the security suites are meaningful and should run. A build-time exclusion would remove that supported configuration.

Whether those suites can run is a property of the cluster the task is pointed at — on a cluster without the security configuration API every PUT /_plugins/_security/api/roles/* returns 400 {"error":"no handler found for uri ..."} — which Gradle cannot determine at configuration time. That case needs a runtime capability check in the tests, not a static exclusion, and is left for separate work.

Related Issues

No separate tracking issue.

Check List

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

The unchecked items are not applicable: this changes a test task's exclusion list and adds no functionality, API surface or user-facing behaviour.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.