MONGOCRYPT-432 Allow keyAltName in encryptedFieldsMap

[mdb-ad]

Background

Adds keyAltName to keyId client-side translation to libmongocrypt that allows users to specify human-readable keyAltName strings instead of binary key IDs.

Implementation

Whenever encryptionInformation is appended to at outgoing command, libmongocrypt looks through the encrypted fields for keyAltName fields and translates them to keyId.

Testing

Tested on the C driver with spec test: https://spruce.mongodb.com/version/697803dbc0c964000764d2a4/

[kevinAlbs]

I expect the "create" command is not translating a "keyAltName":

{
    "create": "coll",
    "encryptedFields": {
        "fields": [
            {
                "path": "secret",
                "bsonType": "string",
                "keyAltName": "keyDocumentName"
            }
        ]
    }
}

See this test to exercise this scenario.

Without support for the "create" command or ClientEncryption.createEncryptedCollection helper, I expect keyAltName may be difficult to use (creation would still require a key ID).

If this is a significant effort, consider filing a MONGOCRYPT ticket to track supporting "create", and update the scope to note this as future work.

[kevinAlbs]

When mongocrypt_setopt_bypass_query_analysis is called, the MONGOCRYPT_CTX_MARKINGS state appears to be incorrectly entered. See this test.

[kevinAlbs]

_fle2_collect_keys_for_compaction requests keys by ID. I expect it will also need to request keys by keyAltName.

Suggest implementing this draft test of the compact command with keyAltname. It currently fails with:
expected UUID for key id.