Update how PyMongo handles UUIDs

[luandy64]

Description of change

This PR sets the PyMongo client to use the "standard" representation of UUID instead of the default "undefined" representation.

From the docs:

uuidRepresentation: The BSON representation to use when encoding from and decoding to instances of UUID. Valid values are the strings: “standard”, “pythonLegacy”, “javaLegacy”, “csharpLegacy”, and “unspecified” (the default). New applications should consider setting this to “standard” for cross language compatibility.

I found this section of the PyMongo docs that gives good background behind the issue here.

QA steps

• [ ] automated tests passing
• [ ] manual qa steps passing (list below)

Risks

I don't think anyone is leaning on the current representation of UUID. It seems to be broken in terms of our syncing.

Rollback steps

• revert this branch