build: fix lint errors and introduce CI check

[JustinBeckwith]

While working on a different task, I tried running npm run lint:fix in hopes of making sure my PR was clean and tidy. It generated ... a lot of unrelated changes. This PR does a few things:

• Runs npm run lint:fix to capture low hanging fruit
• Manually fixes issues standard couldn't automatically fix
• Introduces a new CI check to ensure the linter passes

Happy to discuss any changes!

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.11%. Comparing base (5a0bf7e) to head (e6c090c).
⚠️ Report is 2096 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1277      +/-   ##
==========================================
- Coverage   94.11%   94.11%   -0.01%     
==========================================
  Files          44       44              
  Lines        4097     4096       -1     
==========================================
- Hits         3856     3855       -1     
  Misses        241      241              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[JustinBeckwith]

I'm at a bit of a loss .... npm run lint passes locally with the latest LTS release, but seems to be not passing in CI!? I'll keep poking, but wondering if others have any ideas.

[KhafraDev]

sameOrigin is a utility method exported in lib/fetch/util.js; error wasn't caught before because the previous condition isn't possible. It definitely isn't a global 😄.

edit: fixed in 09f00fb?

[JustinBeckwith]

yuuuuuup, that was it :) I was thinking "surely this isn't just broken" :)

[mcollina]

lgtm