feat!(NODE-4706): validate Timestamp ctor argument

[nbbeeken]

Description

What is changing?

Completed in this PR as well:
https://jira.mongodb.org/browse/NODE-4705

• Updating TS to 4.9 is motivated by getting the type narrowing features of the in operator working
• That removes the need for isObjectLike, I added tests for isDBRefLike, but the logic has not been changed
• Validates Timestamp ctor argument. I went with a verbose approach, given this has been a site of errors and confusion it seems worth raising errors for each possible input mistake that we can catch.
• Adds a type declaration for bigint as an input for Timestamp, this already worked at runtime, NODE-4705 was filed to only to remove support for the two low/hight number inputs, so bigint should keep working.

What is the motivation for this change?

Double check the following

• Ran npm run lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[durran]

Apologies for the nit-picky testing suggestions. Just want to keep to the "tests as documentation" mantra and align with our agreed standards. :)

[nbbeeken]

@durran Love the test improvements, I did it locally to make the linter happy with the formatting etc, let me know if I got all the changes in

[durran]

@durran Love the test improvements, I did it locally to make the linter happy with the formatting etc, let me know if I got all the changes in

Looks great. Thanks!

[durran]

@nbbeeken Can we rebase and resolve conflicts? Then I think we're good to merge.

[nbbeeken]

@durran Updated!