feat(NODE-4406): direct EJSON stringification for UUIDs

[aditi-khare-mongoDB]

Description

What is changing?

ESJON now supports direct stringification of UUID, without needing to call UUID.toBinary() in the argument.

Is there new documentation needed for these changes?

Yes

What is the motivation for this change?

EJSON.stringify({ u: new UUID() }); used to result in an error, but now it is a valid operation

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

[addaleax]

Looks good to me!

I'd be curious to hear from the team on what the line of thought behind not making UUID a subclass of Binary – when the UUID class was first introduced, I thought that was done specifically because it was not intended to work with bson/EJSON serialization/deserialization, but since that's being changed, I'm wondering why UUID is not implemented that way.

[nbbeeken]

Good idea, I suppose if we subclassed we would inherit all the EJSON logic both to and from 🤔
I'll bring this up in the team channel as an alternative approach, I think it's the right idea

Subclass work

[durran]

Closed in favor of #512