Allow primary keys to contain address columns sorted by their resolved values.

[nicktobey]

This is the Doltgres part of this change.

GMS PR: dolthub/go-mysql-server#2854
Dolt PR: dolthub/dolt#8870

The goal of the change is to allow for indexes to use an out-of-line variable-length type (like TEXT or BLOB) as a primary key while still storing just the address in the index (instead of being forced to store a prefix of the value).

As a result of this change, any tuple comparison operation may need to resolve a hash in the NodeStore. This poses two complications:

1. The tuple logic exists at a much lower level than the node store and can't depend on it without creating a dependency cycle. We get around this with a new ValueStore interface that can store and retrieve variable-length bytestrings by their content hash. NodeStore is the only implementation of this interface, but decoupling the interface from the implementation allows us to not depend on NodeStore's internals when passing it to lower-level code.

2. Tuple comparison operations can now end up doing disk IO, which means they need a context parameter.

[github-actions]

	Main	PR
covering_index_scan_postgres	360.93/s	${\color{red}DNF}$
index_join_postgres	152.92/s	${\color{red}DNF}$
index_join_scan_postgres	184.43/s	${\color{red}DNF}$
index_scan_postgres	12.48/s	${\color{red}DNF}$
oltp_point_select	2825.16/s	${\color{red}DNF}$
oltp_read_only	1889.91/s	${\color{red}DNF}$
select_random_points	112.43/s	${\color{red}DNF}$
select_random_ranges	131.19/s	${\color{red}DNF}$
table_scan_postgres	11.22/s	${\color{red}DNF}$
types_table_scan_postgres	5.58/s	${\color{red}DNF}$

[github-actions]

	Main	PR
Total	42090	42090
Successful	15654	15657
Failures	26436	26433
Partial Successes1	5212	5213

	Main	PR
Successful	37.1917%	37.1989%
Failures	62.8083%	62.8011%

${\color{lightgreen}Progressions (3)}$

domain

QUERY: select '{1,2,3}'::dia;

with

QUERY: SELECT count(*) FROM (
    WITH RECURSIVE t(n) AS (
        SELECT 1 UNION ALL SELECT n + 1 FROM t WHERE n < 500
    )
    SELECT * FROM t) AS t WHERE n < (
        SELECT count(*) FROM (
            WITH RECURSIVE t(n) AS (
                   SELECT 1 UNION ALL SELECT n + 1 FROM t WHERE n < 100
                )
            SELECT * FROM t WHERE n < 50000
         ) AS t WHERE n < 100);

QUERY: WITH RECURSIVE
   x(id) AS
     (VALUES (1) UNION ALL SELECT id+1 FROM x WHERE id < 5),
   y(id) AS
     (VALUES (1) UNION ALL SELECT id+1 FROM x WHERE id < 10)
 SELECT y.*, x.* FROM y LEFT JOIN x USING (id);

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. ↩

[zachmu]

LGTM

[nicktobey]

#1224 shows that CI passes once this gets combined with the changes from #1219