support multiple modes of execution for fastfield range query

[trinity-1686a]

in quickwit, we found that some query are faster when range queries are done through the ast, using fastfield-based range query, but some others prefer post filtering done inside the collector. This hints toward implementing two forms of fastfield-based range query, the current one when the range is very selective, and the "more naive filtering" when the range isn't very selective. The selection would also depend on how costly the rest of the query is, costlier queries tends to favor the currently present query, while cheaper queries seems to prefer filtering