fix(remix): Drop Remix 3 release candidates from the peer range (#25808)

**Why:** Remix 3.0.0 stable is out, nothing depends on the release
candidates, and `3.x` matches our other peer ranges.

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Author: chargome

packages/remix/package.json

@@ -106,7 +106,7 @@
     "@remix-run/react": "2.x",
     "@remix-run/server-runtime": "2.x",
     "react": "18.x",
-    "remix": ">=3.0.0-rc.1 <4"
+    "remix": "3.x"
   },
   "scripts": {
     "build": "run-p build:transpile build:types",

packages/remix/test/v3-exports.test.ts

@@ -40,11 +40,9 @@ describe('Remix 3 exports', () => {
   describe('the Remix 3 peer range', () => {
     const range = packageJson.peerDependencies.remix;
 
-    // Asserted by behaviour, so the range can change after Remix 3 reaches GA without failing here.
-    it('accepts release candidates', () => {
-      // `3.x` does not match `3.0.0-rc.1`: semver ranges exclude prereleases unless they name one.
-      expect(semver.satisfies('3.0.0-rc.1', range)).toBe(true);
-      expect(semver.satisfies('3.0.0-rc.2', range)).toBe(true);
+    it('rejects release candidates', () => {
+      expect(semver.satisfies('3.0.0-rc.1', range)).toBe(false);
+      expect(semver.satisfies('3.0.0-rc.5', range)).toBe(false);
     });
 
     it('accepts stable 3.x', () => {