https://github.com/mongodb/node-mongodb-native/commit/f6d7868fab55aa5b51d181f5268879280303f929 made the options property on the MongoClient class a regular enumerable property rather than a symbol property with a corresponding getter.

This breaks the compass-e2e-tests__CSFLE___QE_server_version_gte_7.0.0_when_fleEncryptedFieldsMap_is_not_specified_while_connecting.can_create_a_fle2_collection_with_encryptedFields and compass-e2e-tests__CSFLE___QE_server_version_gte_7.0.0_when_fleEncryptedFieldsMap_is_specified_while_connecting.can_create_a_fle2_collection_without_encryptedFields tests for some reason, where the badge that should be displayed in the UI for Queryable Encryption collections is not displayed, e.g. in https://spruce.mongodb.com/task/10gen_compass_main_test_packaged_app_ubuntu_test_packaged_app_2_patch_bc69d47e19377a0bcdd6c2e4e8e42c1cf264b252_67c08d1991894000075f1a62_25_02_27_16_04_44?execution=2&sortBy=STATUS&sortDir=ASC in Linux CI.

We can work around this by restoring the property's non-enumerable status but should investigate why specifically this type of breakage occurs. The Compass adaptCollectionInfo code correctly identifies the collection as a QE (fle2) collection.