opt: inverted index improvements

[mgartner]

This issue tracks improvements that could be made to inverted indexes.

• enable histogram statistics for JSON and ARRAY inverted index scans opt: ensure statistics builder correctly estimates selectivity of b @> '[]' and b @> '{}' #56870
• calculate statistics for the JSON fetch val and equality operator opt: calculate statistics for the JSON fetch val and equality operator #55319
• generate inverted index scans for chained JSON fetch value operators with equality expression opt: generate inverted index scans for chained JSON fetch value operators with equality expression #55317
• partitioned inverted indexes sql: Partitioning for Inverted Indexes #43643
• index accelerate the -> JSON fetch value operator when the result is equal to an object or array, e.g. j->'a' = {"a": "b"} opt: inverted-index accelerate filters of the form j->'a' = '{"b": "c"} #59605
• enable usage of inverted index with OR clauses opt: enable usage of inverted index with OR clauses #47340
• sqlsmith should generate random inverted indexes
• sqlsmith should generate random multi-column inverted indexes
• generate inverted index scans for JSON fetch value and containment operators opt: generate inverted index scans for JSON fetch value and containment operators #55318
• index accelerate JSON filters in the form j->'a' @> '1' opt: index accelerate JSON filters in the form j->'a' @> '1' #61430 (possibly a duplicate of above?)
• support indexed key-contains queries in JSON inverted indexes sql: support indexed key-contains queries in JSON inverted indexes #23905
• use inverted indexes to satisfy filters with comparison operators: <, <=, >, >= sql: add support for comparison operators in inverted indexes #35154
• create several alternative plans when inverted index spans are intersected opt: create several alternative plans when inverted index spans are intersected #56868
• use paired joins for left joins with non-covering indices opt: use paired joins for left joins with non-covering indices #55452
• opt: improve cardinality estimate for lookup join that follows an inverted join #55448
• sql: support INVERTED INDEX range scans #24960
• opt: index accelerate array overlap operator && #75477
• plan inverted zig zag joins on multi-column inverted indexes
• plan inverted joins when filters have a -> JSON fetch value operator
• opt: inverted-index accelerate filters of the form j->0 = '{"b": "c"} #94666
• opt: inverted-index accelerate filters of the form j->0 @> '{"b": "c"} #94667
• consider indexed computed column expressions when planning inverted joins (see TODO)
• index accelerate <@, or @> when the indexed column is on the right opt: index accelerate <@ (contained by) expressions for JSON and Array inverted indexes #59763
• store an InvertedConstraint with a SpanExpression in props.Scalar so we can improve selectivity estimates of JSON/Array/spatial predicates. opt: improve selectivity estimation of JSON/Array/Spatial predicates in Select #62835
• implement stats for invertedFilter by supporting INTERSECTION and UNION operations on histograms.
• sql: support inverted index acceleration for json ?, ?|, and ?& text #81114
• opt: normalize JSON subscripting [...] to fetch value operators -> #83441
• opt: inverted-index accelerate queries with filters in the form json->'a' IN (...) #87856
• sql: support inverted indexes with more than one inverted column #91460
• opt: inverted-index accelerate filters of the form: j = ... and j IN (...) #96658
• sql: use like operator with JSON and Inverted Indexes for matching #50345

Jira issue: CRDB-3301