Use Case

As a... Node.js BSON maintainer
I want... to use natural bigint literal syntax
So that... I can write more obvious code and not cast numbers to bigints

User Experience

• After this change BSON will only work on platforms that support bigint literal syntax at parse time.
• Previously BSON's use of BigInt used only the constructor and did so in code paths specifically related to bigint conversion or handling.

Dependencies

• None

Risks/Unknowns

• None

Acceptance Criteria

Implementation Requirements

• Switch BigInt(0xFFFF_FFFF) style bitshift constants to 0xFFFF_FFFFn
  • Consider consolidating these in the constants file
• Remove custom eslint plugin that detected literal usage

Testing Requirements

• Remove testing variant that validated BigInt used only under flagged code paths.

Documentation Requirements

• Update platform requirement documentation in readme if any

Follow Up Requirements

• NODE-4928
• NODE-5390