fix(webapp-graphql-relay)!: require one Relay peer runtime

[artem-korolev]

Summary

• move react-relay and relay-runtime from private production dependencies
  to the exact required 20.1.1 peer pair
• keep the pair as exact development dependencies and document the direct
  install and 2.x migration contract
• add an isolated publish-equivalent npm/pnpm consumer matrix covering tarball
  provenance, singleton identity, CJS/ESM/Vite, strict types, Relay compiler,
  and real provider/hook rendering
• add a major Rush change for only
  @omgjs/labkit-webapp-graphql-relay

Root cause

The package created Relay environments and preloaded query references using
private Relay dependencies while application-owned providers and hooks could
resolve another Relay graph. Stateful Relay objects could therefore cross an
implementation boundary that the package metadata allowed but the library
architecture does not support.

Breaking change

Consumers must directly install the supported pair:

npm install react-relay@20.1.1 relay-runtime@20.1.1

The Rush release preview resolves the package from 2.0.0 to 3.0.0.

Validation

• npm run test:relay-consumer-contract
• npm run rush:install
• npm run rush:build
• npm run rush:lint
• serialized Rush test and verify across all 15 projects
• npm run site:docusaurus:check
• committed Rush change verification against origin/main
• changed-surface Trunk check

The full-repository Trunk scan still reports pre-existing Dockerfile, older
workflow-action, generated changelog, and dependency-advisory findings; no
task-scoped Trunk issue remains.