ci: repair lint setup and run it in CI

[DonIsaac]

What does this PR do?

• Replace eslint with oxlint, which was not configured correctly. Before this PR, bun lint simply crashed.
• Configure oxlint to only look for a set of strictly incorrect code
• Add a lint job to CI. While bun lint will display warnings locally, this job will not.
• Fix error-level lint rule violations found. These are strictly (minor) bug fixes.

How did you verify your code works?

Build + test locally

[robobun]

❌ Your commit 07ddcf6 has 11 failures in #7846:

test/bundler/bundler_compile.test.ts - 2 failing on 🐧 3.20 x64-baseline

test/cli/install/registry/bun-install-registry.test.ts - timeout on 🐧 22.04 x64

test/js/bun/css/doesnt_crash.test.ts - timeout on 🐧 3.20 aarch64

test/v8/v8.test.ts - 22 failing on 🐧 3.20 aarch64

test/v8/v8.test.ts - 22 failing on 🐧 3.20 x64-baseline

test/v8/v8.test.ts - 22 failing on 🐧 3.20 x64

test/js/bun/shell/leak.test.ts - 1 failing on 🐧 20.04 x64-baseline

test/js/bun/shell/leak.test.ts - 2 failing on 🐧 12 x64

test/js/bun/spawn/spawn.test.ts - timeout on 🪟 2019 x64

test/js/node/test/parallel/test-fs-stream-double-close.js - timeout on 🐧 24.04 aarch64

test/js/node/test/parallel/test-net-sync-cork.js - code 1 on 🐧 12 aarch64

test/js/node/test/parallel/test-net-sync-cork.js - code 1 on 🐧 12 x64-baseline

test/js/node/test/parallel/test-net-sync-cork.js - code 1 on 🐧 12 x64

test/js/node/test/parallel/test-net-sync-cork.js - code 1 on 🐧 3.20 aarch64

test/js/node/test/parallel/test-net-sync-cork.js - code 1 on 🐧 3.20 x64-baseline

test/js/node/test/parallel/test-net-sync-cork.js - code 1 on 🐧 3.20 x64

test/js/node/fs/fs.test.ts - timeout on 🪟 2019 x64

test/js/bun/http/serve-body-leak.test.ts - 1 failing on 🪟 2019 x64

test/integration/next-pages/test/dev-server-ssr-100.test.ts - 1 failing on 🪟 2019 x64-baseline

test/integration/next-pages/test/dev-server-ssr-100.test.ts - 1 failing on 🪟 2019 x64

[Jarred-Sumner]

I think we're going to need to be very specific of what files have which linter rules apply. We necessarily do weird things in various tests. Things like ReferenceError should definitely be caught, but most stylistic opinions should be enforced by formatter and not by linter

And I don't think spending the time fixing made-up linter errors is higher priority than improving the Node.js passing test %

[DonIsaac]

@Jarred-Sumner I've greatly narrowed the scope of files subject to linting. You'll find the full list in the ignorePatterns property in oxlint.json. I'm also only checking for correctness issues. I've already found a precedence bug in node:stream.