chore: make react-dom and react-native optional peer dependencies

[Gudahtt]

Explanation

The package @metamask/react-data-query has react-dom and react-native as peerDependencies because they are peer dependencies of a dependency this package uses, @tanstack/react-query. This "forwarding" of peer dependencies is something we started doing in our own packages because it better highlights the legitimate requirements of the package (transitive peer dependencies tend to not get surfaced by package managers when they're not met, you have to dig for it).

However, @tanstack/react-query has these two peer dependencies as optional, as they should be. We forgot to document them as optional.

This resolves an unnecessary peer dependency warning in metamask-extension.

References

N/A

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Low Risk
Packaging and tooling metadata only; no application or library runtime logic changes.

Overview
@metamask/react-data-query now marks react-dom and react-native as optional peer dependencies via peerDependenciesMeta, matching how @tanstack/react-query treats them and stopping spurious peer warnings in consumers like metamask-extension.

The unreleased changelog documents the change, yarn.lock reflects the updated workspace package metadata, and knip.config.ts adds a packages/react-data-query ignoreDependencies entry for those two packages (linked to a known knip issue) so they are not reported as unused when they only exist as forwarded peers.

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