CDRIVER-4657 Prohibit extra fields when matching command subdocuments

[kevinAlbs]

Summary

• Prohibit extra fields when matching command subdocuments in the legacy specification test runner
• Add missing call to visitor_fn when matching arrays
• Copy fle2v2-CreateCollection from mongodb/specifications@e59a0ac

Background & Motivation

Prohibit extra fields when matching command subdocuments

Described in mongodb/specifications#1429. The expected behavior for matching command-started events in the legacy Client-Side Encryption test format is to only allow extra fields at the top level of the command document.

Example expectation:

{
    "command_started_event": {
        "command": {
            "create": "encryptedCollection",
            "encryptedFields": {
                "fields": [
                    {
                        "path": "firstName",
                        "bsonType": "string",
                        "keyId": {
                            "$binary": {
                                "subType": "04",
                                "base64": "AAAAAAAAAAAAAAAAAAAAAA=="
                            }
                        }
                    }
                ]
            }
        },
        "command_name": "create",
        "database_name": "default"
    }
}

Example matching actual event:

{
    "command_started_event": {
        "command": {
            "create": "encryptedCollection",
            "encryptedFields": {
                "fields": [
                    {
                        "path": "firstName",
                        "bsonType": "string",
                        "keyId": {
                            "$binary": {
                                "base64": "AAAAAAAAAAAAAAAAAAAAAA==",
                                "subType": "04"
                            }
                        }
                    }
                ]
            },
            "lsid": {
                "id": {
                    "$binary": {
                        "base64": "RA6ru6SwSfm8XRl6wxPEgQ==",
                        "subType": "04"
                    }
                }
            },
            "$clusterTime": {
                "clusterTime": {
                    "$timestamp": {
                        "t": 1686066552,
                        "i": 4
                    }
                },
                "signature": {
                    "hash": {
                        "$binary": {
                            "base64": "AAAAAAAAAAAAAAAAAAAAAAAAAAA=",
                            "subType": "00"
                        }
                    },
                    "keyId": {
                        "$numberLong": "0"
                    }
                }
            },
            "$db": "default"
        },
        "command_name": "create",
        "database_name": "default",
        "operation_id": {
            "$numberLong": "136170890"
        }
    }
}

Extra fields in the actual event (e.g. lsid) are permitted at the top level of the command document. But extra fields are not permitted in nested documents (e.g. an extra field inside encryptedFields would be considered a mismatch)

The C driver permitted allowing extra fields at any level of the command document. This PR adds additional checks to apm_match_visitor to prohibit extra fields in command subdocuments.