Fix test: use unmapped driver so no bundled policy matches

The test 'leaves compatibility unset when no bundled policy matches this
T3 Code version' was using driver 'codex', which has a matching policy in
the bundled provider-compatibility.v1.json (t3CodeRange >=0.0.0, range
<0.129.0 → broken). This caused buildServerProvider to set status to
'error' with a non-undefined compatibilityAdvisory, contradicting the
test assertions.

Switch to a driver not present in the bundled compatibility map so the
test correctly exercises the no-matching-policy path.

Author: cursoragent

apps/server/src/provider/providerSnapshot.test.ts

@@ -46,8 +46,8 @@ describe("providerModelsFromSettings", () => {
 describe("buildServerProvider", () => {
   it("leaves compatibility unset when no bundled policy matches this T3 Code version", () => {
     const provider = buildServerProvider({
-      driver: ProviderDriverKind.make("codex"),
-      presentation: { displayName: "Codex" },
+      driver: ProviderDriverKind.make("unmapped-test-driver"),
+      presentation: { displayName: "Test" },
       enabled: true,
       checkedAt: "2026-04-10T00:00:00.000Z",
       models: [],