Migrate from ESLint to Oxlint

TL;DR: ESLint 9 goes EOL in about a week, not all the plugins I was
using support ESLint 10, and Oxlint is associated with the VoidZero
ecosystem that I've already tied myself into with Vite. More thoughts on
this in the branch commits.

This also unblocks my adoption of TypeScript 7, so I can now use Go on
the frontend too, kinda sorta in a way.

Author: featherbread

client/eslint.config.js

@@ -0,0 +1,40 @@
+import { defineConfig } from "oxlint";
+
+import confusingBrowserGlobals from "confusing-browser-globals";
+
+export default defineConfig({
+  plugins: ["eslint", "jsx-a11y", "react", "typescript"],
+  ignorePatterns: ["dist/**/*"],
+  env: {
+    builtin: true,
+  },
+  categories: {
+    correctness: "error",
+  },
+  rules: {
+    "no-array-constructor": "error",
+    "no-case-declarations": "error",
+    "no-empty": "error",
+    "no-fallthrough": "error",
+    "no-prototype-builtins": "error",
+    "no-redeclare": "error",
+    "no-regex-spaces": "error",
+    "no-restricted-globals": ["error", ...confusingBrowserGlobals],
+    "no-unexpected-multiline": "error",
+    "no-var": "error",
+    "prefer-const": "error",
+    "prefer-rest-params": "error",
+    "prefer-spread": "error",
+    "react/display-name": "error",
+    "react/jsx-no-comment-textnodes": "error",
+    "react/jsx-no-target-blank": "error",
+    "react/no-unescaped-entities": "error",
+    "react/no-unknown-property": "error",
+    "react/rules-of-hooks": "error",
+    "typescript/ban-ts-comment": "error",
+    "typescript/no-empty-object-type": "error",
+    "typescript/no-explicit-any": "error",
+    "typescript/no-require-imports": "error",
+    "typescript/no-unnecessary-type-constraint": "error",
+  },
+});