Currently, anyone is allowed to set the contention factor max of a FLE2 encrypted field to any value in the range 0 to INT64_MAX. Setting it to an absurdly high value may cause issues with FLE2 queries on that field (e.g. slow queries, high compute), since that value dictates how many times binary searches for tag counters in the ESC must be performed.

To mitigate this issue, during create collection, we have to enforce a limit on the contention field of the QueryTypeConfig(s) of every encrypted field in the schema. In addition, during a FLE2 query rewrite of a FLE2 find payload, we need to check that the contention max found in the payload does not exceed this limit, or otherwise the query should be rejected.