Bug fix: ensure OR expressions on a single table use an index when possible

[zachmu]

This fixes the performance regression in select_random_ranges, which uses BETWEEN .. OR BETWEEN .. in its filters.

Requires dolthub/go-mysql-server#3347

[github-actions]

	Main	PR
covering_index_scan_postgres	560.91/s	559.76/s	-0.3%
index_join_postgres	133.60/s	133.20/s	-0.3%
index_join_scan_postgres	190.52/s	190.79/s	+0.1%
index_scan_postgres	11.96/s	11.95/s	-0.1%
oltp_point_select	2420.40/s	2425.62/s	+0.2%
oltp_read_only	1747.26/s	1754.90/s	+0.4%
select_random_points	118.91/s	118.03/s	-0.8%
select_random_ranges	45.80/s	${\color{lightgreen}450.67/s}$	${\color{lightgreen}+883.9\%}$
table_scan_postgres	11.84/s	11.87/s	+0.2%
types_table_scan_postgres	5.44/s	5.45/s	+0.1%

[github-actions]

	Main	PR
Total	42090	42090
Successful	17304	17304
Failures	24786	24786
Partial Successes1	5596	5596

	Main	PR
Successful	41.1119%	41.1119%
Failures	58.8881%	58.8881%

Footnotes

1. These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct. ↩

[Hydrocharged]

Overall looks fine, but as mentioned in the GMS PR, you should add this to sql.EngineOverrides instead of replacing another function within Init. Right now we're assembling everything in the servercfg, but I'm going to be changing that today since it's causing issues with hosted deployment and I need to get a fix out for that quickly, but for everything new, it should go in the overrides.