Added proper dolt_branch_control functionality

[Hydrocharged]

Fixes:

• INSERT INTO dolt_branch_control fails with "non-Doltgres type found in destination #2435

This fixes two primary issues with dolt_branch_control. The first is that we'd error when encountering a destination GMS type, as we make the assumption that all GMS types have been handled once we reach a certain point in the analyzer. This is false for Dolt system tables that may be modified, so now cast those types to their closest Doltgres type for analysis.

The second fix deals with how superusers are handled between Doltgres and GMS. Doltgres uses its own permission model since it's fundamentally different than GMS' model, but dolt_branch_control internally checks for a superuser (or pseudo-superuser) to allow some commands without explicit privileges given. This adds a layer of indirection so that checks for superusers specifically will work as expected.

[github-actions]

	Main	PR
covering_index_scan_postgres	580.02/s	578.86/s	-0.2%
index_join_postgres	122.92/s	122.76/s	-0.2%
index_join_scan_postgres	181.50/s	181.88/s	+0.2%
index_scan_postgres	11.01/s	11.11/s	+0.9%
oltp_point_select	2400.74/s	2400.58/s	-0.1%
oltp_read_only	1719.79/s	1723.73/s	+0.2%
select_random_points	111.73/s	111.12/s	-0.6%
select_random_ranges	447.53/s	448.72/s	+0.2%
table_scan_postgres	10.85/s	10.91/s	+0.5%
types_table_scan_postgres	5.03/s	5.04/s	+0.1%

[github-actions]

	Main	PR
Total	42090	42090
Successful	17674	17675
Failures	24416	24415
Partial Successes1	5575	5575

	Main	PR
Successful	41.9910%	41.9933%
Failures	58.0090%	58.0067%

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

random

QUERY: (SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1)
INTERSECT
(SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1)
INTERSECT
(SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1);

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