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_features(id,feature,introduced,deprecated,removed) VALUES('browser','fdv2','4.9',NULL,NULL);
INSERT INTO sdk_features(id,feature,introduced,deprecated,removed) VALUES('react-client-sdk','fdv2','4.1.2',NULL,NULL);
INSERT INTO sdk_features(id,feature,introduced,deprecated,removed) VALUES('react-native','fdv2','10.19',NULL,NULL);

---

Note

Low Risk
Additive metadata-only changes with no runtime or API behavior; suitable for automatic downstream consumption if patch semantics hold.

Overview
Registers the fdv2 SDK feature for three client-side JavaScript stacks, with version introduced values aligned to upstream metadata: browser at 4.9, react-client-sdk at 4.1.2, and react-native at 10.19.

The same entries are propagated through the generated features.json copies (api-js, api/sdkmeta, products) and metadata/launchdarkly_js-core.json so docs, product surfaces, and SDK meta stay in sync. No existing feature rows are removed or altered beyond these additive blocks.

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