Use Case

As a developer
I want to support supported runtime versions of nodejs in zstd
So that dependencies have runtime support parity

User Experience

• v20 of node should be marked as unsupported in package.json. This would be a breaking change. 

Dependencies

• the longer we wait to this, the more frequent we'll collide with unsupported dependency updates (e.g: https://github.com/mongodb-js/zstd/pull/125)

Risks/Unknowns

• This is a breaking change, since it forces the user to upgrade the server runtime that uses this package.

Acceptance Criteria

Implementation Requirements

• bump the suppoted 'engines' matrix in package.json to support >=v22
• remove any runtime tests which rely on v20

Testing Requirements

• We should ensure we pick a minimum version that's compatible with core packages we intend to update (e.g: node-gyp). Analyze the incoming runtime compatibility matrix in the associated packages and find a candidate range

Documentation Requirements

• Updates to the supported runtimes should be communicated upon release

Follow Up Requirements

• N/A