fix(NODE-6608): calculateObjectSize returns the wrong value for bigint

[nbbeeken]

Description

What is changing?

• Introduce a bigint condition to the switch statement in calculateObjectSize that adds 8 to the size
• Introduce a symbol condition that returns 0
• Introduce a default condition that throws an error if there are future js types that the library cannot understand

Is there new documentation needed for these changes?

No

What is the motivation for this change?

This fixes a bug where the serializer produces something of a different size than what the calculate function claims it will.

Release Highlight

Fix calculateObjectSize not accounting for BigInt value size

BSON.calculateObjectSize was missing a condition for BigInt values, meaning it did not account for them in the same way that it would for Long values. This has been corrected.

We also added a new default condition that will catch any new values that may be returned by typeof in the future and will throw an error rather than returning an inaccurate size.

Double check the following

• Ran npm run check:lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket