Terms agg exclude clauses slow on high-cardinality fields

[markharwood]

Even with a single exclude term, a terms aggregation can be very slow to execute on fields with high cardinality.
The culprit is the IncludeExclude.OrdinalsFilter.acceptedGlobalOrdinals method which loops over a globalTermsEnum to produce a set of accepted global ordinals. This can take several seconds and is a cost paid for every query.

The issue #11176 is related to the same use case but is a different problem, relating to the scalability of the exclude list provided.

[markharwood]

Fixed as part of caf7235