fix(metadata): ingest new data and regenerate products

[github-actions]

Metadata has changed. Ensure that the changes obey patch semantics (data added or modified in a non-breaking
way), as upstream services may consume these changes automatically.

INSERT INTO sdk_releases(id,major,minor,patch,date) VALUES('browser',4,9,1,'2026-06-29T19:18:53Z');
INSERT INTO sdk_releases(id,major,minor,patch,date) VALUES('flutter-client-sdk',4,20,0,'2026-06-29T17:49:21Z');
INSERT INTO sdk_releases(id,major,minor,patch,date) VALUES('react-client-sdk',4,1,4,'2026-06-29T19:18:57Z');
INSERT INTO sdk_releases(id,major,minor,patch,date) VALUES('react-native',10,19,1,'2026-06-29T19:18:51Z');

---

Note

Low Risk
Data-only metadata sync with additive release entries and EOL updates; no application logic or security-sensitive code paths change.

Overview
Regenerates SDK release metadata after ingesting upstream sdk_releases data. The visible diff updates flutter-client-sdk only across the mirrored releases.json copies (products/, api/sdkmeta/data/, api-js/src/data/).

Flutter client SDK: Adds 4.20 as the new current line (release date 2026-06-29, eol: null) and sets 4.19’s eol from null to 2027-06-29, matching the usual pattern when a new minor becomes latest and the previous one gets an EOL date.

This is additive, schema-shaped metadata (no API or logic changes); downstream products that read these JSON files may pick it up automatically.

^{Reviewed by Cursor Bugbot for commit 6095a32. Bugbot is set up for automated code reviews on this repo. Configure here.}