Use Case

As a driver engineer,
I want to remove redundant code,
So that we maintain less code.

`enableMultipleCollinfo` was added to ensure that drivers < 6.14 were compatiable with mongodb-client-encryption >=6.3.  Once we no longer need to support this compatibility matrix, we can remove this option from mongodb-client-encryption and the FLE bindings.

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Acceptance Criteria

Implementation Requirements

• Remove support for `enableMultipleCollinfo` from mongodb-client-encryption.
• Remove `enableMultipleCollinfo` from the options passed to MongoCrypt's constructor in the driver.
• Remove unnecessary testing from client_side_encryption.prose.25.lookup.test.ts in the driver.

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward