docs: drop migrated TeamAndUserSelectItem from Button ref sweep

[detail-app]

Describe your changes:

Fixes #N/A — automated doc-drift fix (no issue).

I worked on docs/antd-migration/button.md because commit 2edf277 migrated
TeamAndUserSelectItem.tsx away from antd Button to
@openmetadata/ui-core-components, but the antd Button -> core migration
guide still listed components/Alerts/DestinationFormItem/TeamAndUserSelectItem/TeamAndUserSelectItem.tsx:238
as a live <Button ref={...}> site to convert and claimed "5 live usages".
An agent or developer running the ref codemod sweep would open the file, find
no antd Button to convert (the trigger is now a <div role="button">),
and hit a count mismatch. Removed the stale site and corrected the count from
5 to 4 in both the "No direct equivalent" gap table and the hand-finish
punch list.

Type of change:

• Documentation

High-level design:

N/A — small change.

Tests:

Not applicable — documentation-only change.

UI screen recording / screenshots:

Not applicable.

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation> — N/A, no linked issue.
• My PR is linked to a GitHub issue via Fixes #<issue-number> above. — N/A.
• I have commented on my code, particularly in hard-to-understand areas. — N/A, doc-only.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed. — N/A.
• For UI changes: I attached a screen recording and/or screenshots above. — N/A.
• I have added tests (unit / integration / Playwright as applicable) and listed them above. — N/A, doc-only.

Introduced by commit 2edf277 (@shah-harshit, #32078)

---

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 d0ae15d4f8d25a416b39760b0a18cfafb6e4deda in Playwright run 34069267393, attempt 1.

✅ 557 passed · ❌ 0 failed · 🟡 0 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) 38m 1s

⏱️ Max setup 4m 32s · max shard execution 20m 1s · max shard-job elapsed before upload 23m 7s · reporting 5s

🌐 234.37 requests/attempt · 2.82 app boots/UI scenario · 21.23% common-shard skew

Optimization targets still in progress:

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

Shard	Passed	Failed	Flaky	Skipped	Lifecycle failed	Lifecycle flaky
✅ Shard chromium-01	135	0	0	0	0	0
✅ Shard chromium-02	135	0	0	0	0	0
✅ Shard chromium-03	129	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

📦 Download artifacts

How to debug locally

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