FieldIndexHoles not being used by DefaultQueryPlanner

[ivakegg]

FederatedQueryPlanner issues:

1. The FederateQueryPlanner shall be renamed to the DatePartitionedQueryPlanner
2. The original IndexHole needs to be renamed to a IndexValueGap, and FieldIndexHole to IndexFieldGap
3. The FederatedQueryPlanner.isInDateRange is not handling overlaps of the endDate correctly
4. The date type is not being applied prior to determining the index holes which results is the initial partitioning being incorrect
5. The FederateQueryPlanner is expanding unfielded terms but the query tree is not preservered which means that the
   default query planners are doing the same work all over again
6. The DefaultQueryPlanner is using a static set of indexed fields which basically means FieldIndexHoles are being ignored
   6a) The DefaultQueryPlanner should apply FieldIndexHoles in a mannor similar to the ValueIndexHoles
   6b) OR the set of indexed and reverse indexed fields should be pulled based on the date range.

Consider doing the default query planning completely up front, then partition the query plans and push down terms in each partition based on the field index holes