ci(external-it): retry dependency build on transient mirror failures

[mohityadav766]

What

2.0 parity for #30590. Wraps the Build dependencies for integration-tests step (mvn -DskipTests install -pl :openmetadata-integration-tests -am) in all three external-IT jobs (ui / search / scale) in a 3× retry loop.

Why

A single transient dependency-fetch failure kills the job before any test runs — the resolution had no retry, unlike the login step (curl --retry 5). Different artifact every failing run ⇒ transient, not a real dependency problem. Warn+sleep only when a retry follows; terminal ::error:: on final failure (review feedback from #30590 already incorporated here).

Notes

• The reindex test-hardening that went to 1.13 in #30589 is already present on 2.0 (identical to main), so no test backport is needed here.
• The collate-ci nightly (pulp mirror) build retry lives in openmetadata-nightly#263 and is ref-agnostic, so it already covers 2.0 runs. This PR only adds the generic Maven-Central retry to 2.0's in-repo ubuntu-latest workflow.
• Bounded mitigation: rides out transient errors, not a sustained mirror outage.

🤖 Generated with Claude Code

Greptile Summary

Adds bounded Maven build retries to all three external integration-test jobs.

• Retries dependency builds up to three times.
• Waits 30 seconds between attempts.
• Preserves a failing step after the final unsuccessful attempt.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking diagnostics issue where arbitrary Maven failures are labeled as dependency-mirror failures.

The bounded loops preserve terminal failure and successful retries, but their annotations assert a failure category that the exit-code-only logic does not establish.

Files Needing Attention: .github/workflows/java-playwright-external.yml

Important Files Changed

Filename	Overview
.github/workflows/java-playwright-external.yml	Adds equivalent retry loops to the UI, search, and scale external-IT dependency builds; the loops work but overstate the cause of arbitrary Maven failures.

_{Reviews (1): Last reviewed commit: "ci(external-it): retry dependency build ..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[github-actions]

❌ PR checklist incomplete

This PR cannot be merged until the following are addressed on its linked issue:

• No GitHub issue is linked. Link an issue in the Development section of the PR (or add Fixes #12345 to the description). For a same-org cross-repo issue, add Fixes open-metadata/<repo>#123 to the description.

The fields live on the linked issue in the Shipping project (open the issue → right sidebar → Projects). After you set them, re-run this check (or push a commit) — issue/project changes do not re-trigger it automatically.

Maintainers can bypass this check by adding the skip-pr-checks label.

[gitar-bot]

Code Review ✅ Approved

Adds a retry loop to the dependency build step across external-IT workflows to handle transient mirror failures. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar | Powered by Gitar — free for open source}

[greptile-apps]

Unverified Maven failure labels

The loop classifies every nonzero Maven exit as a transient dependency-mirror failure, including deterministic compilation, plugin, formatting, and configuration errors. This produces misleading warning and terminal annotations that delay diagnosis of the actual build failure.