docs: drop stale Playwright wrapper/job-clock minute values from README

[detail-app]

Describe your changes:

Removed the hardcoded "25-minute timeout wrapper" and "35-minute
playwright-ci job clock" figures from .github/playwright/README.md,
replacing them with a pointer to playwright-e2e-reusable.yml. These
figures were stale: the wrapper and job clock have since moved to 60m
and 75m respectively, so the README described a 25-minute ceiling that
no longer constrains the shard allocation budget.

A developer or agent reasoning about shard-budget headroom against the
README would believe the 21-minute allocation budget must stay under a
25-minute wrapper, when the real wrapper is 60m — leading to wrong
conclusions about how much headroom exists and whether a budget bump is
safe.

Introduced by commit 8fb5397 (@pmbrull, #32611)

Type of change:

• Documentation

High-level design:

N/A — small change.

Tests:

Not applicable — documentation-only change with no code or behavior
impact.

UI screen recording / screenshots:

Not applicable.

Checklist:

• I have read the CONTRIBUTING document.

---

Doc Drift PRs can be configured here.

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[github-actions]

✅ Playwright Results — workflow succeeded

Validated commit 11e6026edca3d5c0b5eed550571581c57ba84b74 in Playwright run 34069118206, attempt 1.

✅ 556 passed · ❌ 0 failed · 🟡 1 flaky · ⏭️ 0 skipped · 🧰 0 lifecycle flaky

Performance

Blocking targets: ✅ met · Optimization targets: 🟡 in progress

Shard-job maxima below are not the full workflow wall time; the linked run includes build, fixture, planning, and reporting.

🕒 Full workflow signal wall (to summary) 32m 39s

⏱️ Max setup 4m 17s · max shard execution 13m 58s · max shard-job elapsed before upload 17m 20s · reporting 5s

🌐 234.49 requests/attempt · 2.82 app boots/UI scenario · 27.09% common-shard skew

Optimization targets still in progress:

• Common shard skew was 27.09% (convergence target: at most 15%).
• Browser traffic was 234.49 requests per attempt (convergence target: fewer than 200).
• Application boot ratio was 2.82 per UI scenario (1633 boots / 579 scenarios; convergence target: at most 1).

Shard	Passed	Failed	Flaky	Skipped	Lifecycle failed	Lifecycle flaky
✅ Shard chromium-01	102	0	0	0	0	0
🟡 Shard chromium-02	99	0	1	0	0	0
✅ Shard chromium-03	91	0	0	0	0	0
✅ Shard chromium-04	106	0	0	0	0	0
✅ Shard data-asset-rules-01	65	0	0	0	0	0
✅ Shard domain-isolation-01	16	0	0	0	0	0
✅ Shard global-state-01	34	0	0	0	0	0
✅ Shard ingestion-01	1	0	0	0	0	0
✅ Shard reindex-01	2	0	0	0	0	0
✅ Shard search-01	11	0	0	0	0	0
✅ Shard search-rbac-01	29	0	0	0	0	0

🟡 1 flaky test(s) (passed on retry)

• Pages/Entity.spec.ts › Tag Add, Update and Remove (shard chromium-02, 1 retry)

📦 Download artifacts

How to debug locally

# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip    # view trace