react-meteor-data: support typescript@6 (v4.1.0-beta.0)

[italojs]

Problem

The published react-meteor-data derives its typescript dependency constraint from api.versionsFrom(['1.8.2', '1.12', '2.0', '2.3', '3.0']), which resolves to:

typescript@3.7.0 || 4.1.2 || 4.1.2 || 4.3.2 || 5.4.3

Every entry is capped below 6.0.0 (Meteor's @X.Y.Z means >=X.Y.Z <(X+1).0.0). Meteor is now moving to TypeScript 6 in meteor/meteor#14560, which bumps the typescript package to 6.0.3. On that release, resolving react-meteor-data fails:

error: Conflict: Constraint typescript@3.7.0 || 4.1.2 || 4.1.2 || 4.3.2 || 5.4.3
is not satisfied by typescript 6.0.3.
* typescript@6.0.3 <- top level
* typescript@3.7.0 || 4.1.2 || 4.1.2 || 4.3.2 || 5.4.3 <- react-meteor-data 4.0.1

This is what breaks the ecmascript-regression self-test (group 7) on that PR.

Fix

TypeScript 6 is not part of any published Meteor release yet, so it can't be pulled in through api.versionsFrom. Instead, set the supported typescript range explicitly and add 6.0.0, keeping the existing lower versions for backwards compatibility:

const TYPESCRIPT_VERSIONS = 'typescript@3.7.0 || 4.1.2 || 4.3.2 || 5.4.3 || 6.0.0'

Applied to both onUse and onTest. Version bumped to 4.1.0-beta.0 (beta).

Note: once a Meteor release shipping TypeScript 6 is published, this can move back to a plain api.use('typescript') by adding that release to versionsFrom.

Testing

Verified locally against a Meteor checkout with the typescript package bumped to 6.0.3:

• Before (published react-meteor-data@4.0.1): fails with the conflict above.
• After (4.1.0-beta.0 from this branch): resolves cleanly —

react-meteor-data  4.1.0-beta.0+  React hook for reactively tracking Meteor data
typescript         6.0.3+         Compiler plugin that compiles TypeScript and ECMAScript...