Added two more distancefilter benchmarks and updated iterations after new optimizations

[craigtaverner]

The recent optimization of ESQL distance-sort allows us to benchmark that properly. That PR also did a few bug-fixes to distance filtering, so we added an alternative version of the query that is now also optimized.

[iverase]

Use a filter instead of must?

[iverase]

Instead of a must not, could we use a disjoint spatial relationship?

[craigtaverner]

The disjoint version was the original version. This is an alternative query that deliberately does things differently, to see if that makes a difference to the performance. It does not seem to make any difference.

[iverase]

I think we can improve the _search, wdyt?

[craigtaverner]

I think we can improve the _search, wdyt?

The original distanceFilterCount200x300 has been there for a few months. This new distanceFilterCount200x300-alt is deliberately an alternative way of doing the same thing, in particular the must_not approach instead of a disjoint. The benchmark is simply testing whether there is any performance difference between the two approaches.