This ticket will involve adding a new QueryType to the relevant IDL file and adding unit tests to make sure that the a parsed schema tree can contain a range index.

Parsing the query type config into a SchemaTree requires adding support for range indexes in ResolvedEncryptionInfo. Range will need to be added as a type to the `Fle2AlgorithmInt` struct.

There are other optional fields that are only relevant for the range index described in the product description:

{
          "queryType": "range", //required
          "min" : Number/Date,        // optional, only for range
          "max" : Number/Date,        // optional, only for range
          "sparsity" : Number,        // optional, only for range
          "contention": Number        // optional
       }

Information on the IDL: https://wiki.corp.mongodb.com/display/HGTC/Using+IDL+for+Code+Generation+in+the+Server