Today, it is only possible to create a UUID value via the JSON view in Compass by using the binary representation and explicitly specifying the subtype. We should make it possible to create and edit UUID values with the new UUID 4 subtype and each of the different legacy UUID encodings so that users have an easy, native way to work with UUID values. We are adding support for legacy UUIDs given the fact that 30% of Compass users that view data containing UUIDs in Compass are using UUIDs with subtype 3. We do not think it is feasible to expect all of these users to migrate their data to subtype 4. 

When releasing this ticket, we need to notify users about the fact that they need to pay attention to which UUID type they select. We should be able to detect which users are viewing data with subtype 3 to notify them accordingly. (We can accomplish this via guide cue or Intercom)

For the legacy UUID types, we should create 3 separate types to represent the different encodings:  LegacyJavaUUID, LegacyCSharpUUID, LegacyPythonUUID