feat(NODE-4855): add hex and base64 ctor methods to Binary and ObjectId

[nbbeeken]

Description

What is changing?

Adds APIs to create BSON Binary / UUID / ObjectId types from hex and base64 strings.

class ObjectId {
  static createFromHexString(hex: string): ObjectId;
  static createFromBase64(base64: string): ObjectId;
}

class Binary {
  static createFromHexString(hex: string, subType? number): Binary;
  static createFromBase64(base64: string, subType? number): Binary;
}

class UUID extends Binary {
  static override createFromHexString(hex: string): UUID;
  static override createFromBase64(base64: string): UUID;
}

Also corrects Binary.prototype.inspect to print a roundtrip empty instance. As well as use the new base64 helper for more concise usage.

> new Binary()
Binary.createFromBase64("", 0)

> new Binary(null, 0x23)
Binary.createFromBase64("", 35)

> new Binary(Buffer.from('🤓', 'utf8'), 0x7F)
Binary.createFromBase64("8J+kkw==", 127)

What is the motivation for this change?

Printing out Buffer.from() as the first argument to Binary was clunky and didn't provide the best way to reproduce a Binary instance from the visible output.

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
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[nbbeeken]

We had a bug here where the default new Binary() printed:

Binary(Buffer.from("00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", "hex"), 0)

Which isn't the same as what would end up in BSON, b/c position determines how many bytes are serialized. The above constructs a Binary where position is set to 256, instead of set to zero.

[nbbeeken]

Looks like a copy pasta mistake, the if stmt asserts for 24 characters, so a 12 byte string wouldn't work here.

[nbbeeken]

Just testing the existing behavior here.

[nbbeeken]

This will throw if we mistakenly introduce a syntax error or if we produce strings that when invoked lead to runtime errors