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]

^{Updated 11:12 PM PT - Jan 7th, 2025}

✅ @DonIsaac, your commit 3eb2827 has passed in #9206! 🎉

---

🧪   try this PR locally:

bunx bun-pr 15720

[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.