Chore: Repro missing built-in rule validation (refs #13793)

The bulk of our tests for rule schemas are isolated unit tests of
`ConfigValidator`. This is a single test to be sure we actually run rule
schema validation end-to-end and prevent cases like #13793.

After I run a patch release of `@eslint/eslintrc`, I'll push a second
commit on this branch to bump the dependency version and fix the test.

tests/lib/eslint/eslint.js

@@ -3919,6 +3919,26 @@ describe("ESLint", () => {
 
             await assert.rejects(() => eslint.calculateConfigForFile(null), /'filePath' must be a non-empty string/u);
         });
+
+        // https://github.com/eslint/eslint/issues/13793
+        it("should throw with an invalid built-in rule config", async () => {
+            const options = {
+                baseConfig: {
+                    rules: {
+                        "no-alert": ["error", {
+                            thisDoesNotExist: true
+                        }]
+                    }
+                }
+            };
+            const engine = new ESLint(options);
+            const filePath = getFixturePath("single-quoted.js");
+
+            await assert.rejects(
+                () => engine.calculateConfigForFile(filePath),
+                /Configuration for rule "no-alert" is invalid:/u
+            );
+        });
     });
 
     describe("isPathIgnored", () => {