feat: support node 22

[llimllib]

🚥 Resolves ISSUE_ID

🧰 Changes

• get the tests passing locally
  • I'm going to defer this. The tests aren't passing locally because they're reading my global git config, I think, so I'm going to rely on CI for now
• update the test action with a node version matrix
• get the tests running on macos newer than 13
  • there's a single test that fails, consistently, on macos > 13
• add tests to the publish job
  • we don't want to publish versions that don't pass the tests
  • gonna add this in the future, but trusting the tests in CI for now. I remvoed it because it was too much setup in the cross-compile jobs to fit comfortably in this PR
• update the publish job to include node 22 prebuilds
  • we're gonna have super fat binaries until we can get an optionalDependencies-style setup going
• run linux-arm tests on PRs
• fix the issue uncovered by running the linux-arm tests
  • cf Linux ARM appears to have a memory handling bug nodegit/nodegit#2024 , I'm going to push this off so I can get a release out and proceed with other changes, but I think this is a memory leak bug
• update version number

The patch in this commit resolves the build issue noted in nodegit#2023 by applying a patch to zlib, which is a little gross but gets us building at least

[erunion]

good idea

[erunion]

Why exclude node_modules but allow test? Are we running tests in the Docker container?

[llimllib]

• node_modules is excluded because the docker container may have a different arch so native builds will not work
• test was excluded to speed up cross-compilation but:
  • it's tiny so kind of useless
  • I want to run the tests on cross-compiles before releasing. I actually had it in this PR but it was too much work so I pushed it off to the future

[erunion]

not that it would be accepted in a timely manner but should this get upstreamed?

[llimllib]

I left a comment on their issue tracker, I'm not gonna bother with a PR because the maintainer doesn't seem to accept them

(If you're the maintainer reading this though, hmu I'd be happy to PR a fix with you)