Use Case

As a Node driver developer,
I want the compiler to know about the built-ins Node 22 actually provides,
So that we don't hand-roll or guard APIs that exist in every supported runtime.

Risks/Unknowns

• Only safe once Node 22 is the minimum supported version, so this depends on NODE-7706.

Acceptance Criteria

Implementation Requirements

• Raise lib from es2023 to es2024 in the driver's tsconfig.json, matching the Node 22 baseline recommended by @tsconfig/node22
• Leave target at ES2023. @tsconfig/node22 recommends target: es2022, so ES2023 already meets the Node 22 baseline, and es2024 corresponds to Node 24.
• Apply the same change to the other published packages that set lib explicitly

Testing Requirements

• Existing build and type tests pass
• api-extractor output is unchanged, confirming no public type surface change

Documentation Requirements

• Update the TypeScript and ECMAScript target statements in the driver README if either value changes

Follow Up Requirements

• None