Sync with Comcast upstream and republish @grafana/react-data-grid (auto-height, a11y, npm publishing)

[fastfrwrd]

Brings our long-stale main current with Comcast/react-data-grid upstream (a88517cc8) and re-layers Grafana's changes on top, so we can publish a fresh @grafana/react-data-grid from main. #8 merges into this branch first, so merging this PR to main delivers everything below.

Why now

We were blocked from pulling upstream for over a year due to now-resolved tooling limits, and Grafana has moved off React 18 (which is why the old react-18 fork branch existed). This resets main to upstream and keeps only the non-React-18 value.

What's in here

Upstream sync — ~220 upstream commits, bringing the fork to a88517cc8. Ingested under the signed-commits fork-sync exemption (Freshservice #168922, per #platform-productivity-chat).

Auto-height (upstream PR Comcast#4040 re-layered) — dynamic row heights for non-virtualized rendering: rowHeight accepts a string (e.g. "auto") with discriminated-union typing, plus PageUp/PageDown paging. Includes test/browser/rowHeight.test.tsx and the DynamicHeightCells example. This is what Grafana's Table panel relies on.

Accessibility — aria-hidden on non-interactive utility elements (drag handle, drag image, measuring cells, scroll-to-position element). Upstream already covers the resize handle and removed the old focus-sink, so those hunks are dropped.

Publish @grafana/react-data-grid from main (rides upstream's npm/tsdown/Node-26 tooling):

• Rename to @grafana/react-data-grid, publishConfig.access: public, version 7.0.0-beta.59, repo/homepage/bugs → Grafana fork.
• ci.yml: version-gated auto-publish job (EndBug/version-check) → npm trusted publishing on push to main when the version changes, then tag + GitHub release.
• Remove Comcast-only tooling that shouldn't run in the fork: publish.yml, update-screenshots.yml, and the gh-pages deploy step (hardcoded Comcast repo URL).
• CODEOWNERS → dataviz-squad; README fork note.

CI hardening for Grafana org rulesets — pin all actions to full SHAs (zizmor unpinned-uses), explicit permissions, persist-credentials: false on the test checkout. package-lock.json root updated for the scope/version (no dependency changes).

Merge order

1. Merge Republish as @grafana/react-data-grid from main: auto-height (#4040), a11y, npm publishing #8 into this branch (chore/sync-comcast-upstream) — a non-default branch, so it's not gated by the zizmor / required-PR rules. This lands the clean ci.yml + workflow deletions here.
2. This PR's checks then go green; merge to main with a merge commit (not squash) so upstream history is preserved.
3. Merging to main trips the version-gated publish job → publishes @grafana/react-data-grid@7.0.0-beta.59.

Publishing note

npm trusted-publisher config must point at this repo's ci.yml workflow (beta.57/.58 published from ci.yml on react-18; same workflow filename).

[github-actions]

Signed commits report

5 of 230 commits between main and chore/sync-comcast-upstream could not be fully verified:

Commit	Author	Reason	Message
1720c1ad	Nicolas Stepien	unsigned	Publish 7.0.0-beta.57
12fb93e0	Nicolas Stepien	unsigned	Publish 7.0.0-beta.58
8a76e9e9	Nicolas Stepien	unsigned	prettier@3.7.4
17d564ba	nstepien	unsigned	7.0.0-beta.59
aec5523d	Nicolas Stepien	unsigned	7.0.0-beta.60

This repository requires all commits to be signed. See GitHub docs on commit signature verification.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ fastfrwrd
❌ nstepien
_{You have signed the CLA already but the status is still pending? Let us recheck it.}