Use Case

As a developer
I want to support supported versions of nodejs in mongodb-connection-string-url
So that dependencies have runtime support parity

User Experience

• v20 if 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/mongodb-connection-string-url/pull/128#issuecomment-5444739412)_

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

• N/A

Documentation Requirements

• Updates to the supported runtimes should be communicated upon release

Follow Up Requirements

• https://jira.mongodb.org/browse/NODE-7801 will be unblocked after this task is complete