In libmongocrypt, mc_FLE2RangeFindSpecEdgesInfo_parse asserts that the trimFactor must be present in the encryption placeholder if the range v2 feature is enabled. This causes an issue because query analysis only sets this field if the trimFactor is explicitly provided in the encrypted fields schema.  However, the work for SERVER-91078 might require the query analysis to always have include a trimFactor specifying the default value to use if the user does not provide an explicit value in the schema. Consider whether the server should always just set the trimFactor for "range" query types.