build: upgrade all the things

[Robbert]

Oops, I accidentally already created a PR.

To do:

• [ ] Discuss: fix eslint no-useless-escape issues removes regexp escapes. However the existing ESLint config specifically disables this rule. Is there a reason the escapes are actually needed? In that case:
  • revert my commit
  • disable no-useless-escape in the new eslint config
• [x] move codecov SaaS to reparate PR
• [x] fix errors
• [x] discuss: fetch is now available in Node.js, and the shim-fetch.js from lib-font is no longer being used. This causes all tests to fail, because local paths are treated differently. I'm not sure if this is a breaking change, or if the fromPath function is already broken in Node 22 in the current release.
  • Update: I investigated the use of fromPath and fromDataBuffer. fromPath is uses in Node.js only, and fromDataBuffer is used in the browser mainly. Making fromPath Node.js only makes sense to me. For browser support I suggest adding a new fromURL API.

[RoelN]

Thanks Robbert! 🙏

I think there's something wrong with the linter/prettier, as running npm run prettier makes changes we don't want, like " → '. Likewise for npm run lint-fix.

Also npm run lint gives ERROR: "lint:prettier" exited with 1. 🤔

The rest of the changes look reasonable to me, but I'd love an extra pair of eyes on this. Maybe @Ryuno-Ki would like to do the honors?