[auto-bump] [no-release-notes] dependency by coffeegoddd

[coffeegoddd]

☕ An Automated Dependency Version Bump PR 👑

Initial Changes

The changes contained in this PR were produced by `go get`ing the dependency.

```bash
go get github.com/dolthub/[dependency]/go@[commit]
```

[github-actions]

	Main	PR
covering_index_scan_postgres	885.72/s	${\color{lightgreen}1109.38/s}$	${\color{lightgreen}+25.2\%}$
index_join_postgres	184.69/s	${\color{red}158.50/s}$	${\color{red}-14.2\%}$
index_join_scan_postgres	195.02/s	194.02/s	-0.6%
index_scan_postgres	11.99/s	11.99/s	0.0%
oltp_point_select	2472.19/s	2482.70/s	+0.4%
oltp_read_only	1708.30/s	1835.94/s	+7.4%
select_random_points	122.74/s	125.17/s	+1.9%
select_random_ranges	757.34/s	${\color{lightgreen}837.36/s}$	${\color{lightgreen}+10.5\%}$
table_scan_postgres	11.48/s	11.87/s	+3.3%
types_table_scan_postgres	5.27/s	5.38/s	+2.0%

[github-actions]

	Main	PR
Total	42090	42090
Successful	18006	18001
Failures	24084	24089
Partial Successes1	5371	5372

	Main	PR
Successful	42.7798%	42.7679%
Failures	57.2202%	57.2321%

${\color{red}Regressions (6)}$

domain

QUERY:          create table dom_table (x inotnull);
RECEIVED ERROR: runtime error: invalid memory address or nil pointer dereference

QUERY:          drop table dom_table;
RECEIVED ERROR: runtime error: invalid memory address or nil pointer dereference

QUERY:          drop domain inotnull;
RECEIVED ERROR: runtime error: invalid memory address or nil pointer dereference

QUERY:          drop function sql_is_distinct_from(anyelement, anyelement);
RECEIVED ERROR: runtime error: invalid memory address or nil pointer dereference

QUERY:          create domain testdomain1 as int;
RECEIVED ERROR: runtime error: invalid memory address or nil pointer dereference

QUERY:          drop domain testdomain1;
RECEIVED ERROR: runtime error: invalid memory address or nil pointer dereference

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

domain

QUERY: select null::inotnull;

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

[github-actions]

This PR has been superseded by #2640