fix: resolve oxlint warnings without removing code

[Vaivaswat2244]

Re-lands #9103, which was reverted in #9160.

Changes:

Resolves all 143 oxlint warnings. npm run lint exits clean. No lint config was changed.

The difference from #9103: no code is removed. Every function, method or field that was previously deleted is reinstated with an oxlint-disable-next-line and a short note saying why it is kept, matching how #determinant4x4 in Matrix.js was already handled. That covers #toColorMode, calculateOffset, destroyClickedElement, getNodeKey, makeGuardedCallbacks, #matrix and the textFont destructure. testImageRender and createDummyFile are commented out alongside their commented-out callers rather than deleted.

What is still changed rather than suppressed:

• unused imports removed
• catch (e) {} becomes catch {}
• == becomes ===
• // falls through on intentional switch fallthroughs
• { } around case bodies containing declarations
• dead if (0) blocks and unreachable post-throw code removed

The duplicate remove() in Renderer3D is left exactly as it is on main, with a no-dupe-class-members suppression, so this PR changes no runtime behaviour. The actual fix for that is a separate PR since it is a behaviour change.

Screenshots of the change:

N/A

PR Checklist

• npm run lint passes
• Inline reference is included / updated (N/A, no public API changes)
• Unit tests are included / updated (N/A, existing suites pass unchanged: 2174 passed, 0 failed)

[p5-bot]

Continuous Release

CDN link

• https://raw.esm.sh/pr/p5@4e2a869/lib/p5.min.js

Published Packages

• https://pkg.pr.new/p5@4e2a869

Commit hash: 4e2a869

Previous deployments

---

This is an automated message.

[ksen0]

Thank you!