Added dropping triggers when dropping a table

[Hydrocharged]

[github-actions[bot]]

	Main	PR
covering_index_scan_postgres	345.35/s	332.84/s	-3.7%
index_join_postgres	150.69/s	150.16/s	-0.4%
index_join_scan_postgres	183.35/s	181.25/s	-1.2%
index_scan_postgres	12.38/s	12.28/s	-0.9%
oltp_point_select	2475.73/s	2461.28/s	-0.6%
oltp_read_only	1785.77/s	1782.13/s	-0.3%
select_random_points	114.19/s	115.87/s	+1.4%
select_random_ranges	130.79/s	126.69/s	-3.2%
table_scan_postgres	11.80/s	11.53/s	-2.3%
types_table_scan_postgres	5.34/s	5.30/s	-0.8%

[github-actions[bot]]

	Main	PR
Total	42090	42090
Successful	16378	16402
Failures	25712	25688
Partial Successes[^1]	5540	5538

	Main	PR
Successful	38.9119%	38.9689%
Failures	61.0881%	61.0311%

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

alter_table

QUERY: insert into parent values (1, 2, 3);

QUERY: insert into child values (12, 13, 'testing');

QUERY: select * from child;

fast_default

QUERY: DELETE FROM leader;

triggers

QUERY: insert into parted_trig values (1), (2), (3);

QUERY: create trigger t before insert or update on parted
  for each row execute function parted_trigfunc();

QUERY: update parted_trigger set a = a + 2;

QUERY: update parted_trigger set b = b || 'b';

QUERY: create trigger tg after insert on parent
  for each row execute procedure trig_nothing();

QUERY: insert into parted_trig (a) values (50);

QUERY: insert into parted_trig (a) values (50);

QUERY: insert into parted_trig (a) values (50);

QUERY: insert into parted_trig (a) values (50);

QUERY: insert into parted_trig (a) values (50);

QUERY: insert into parted_trig (a) values (50);

QUERY: insert into parted_trig (a) values (50);

QUERY: insert into parted_trig (a) values (50);

updatable_views

QUERY: INSERT INTO base_tbl VALUES (1,2), (4,5), (3,-3);

QUERY: SELECT * FROM rw_view1;

QUERY: INSERT INTO base_tbl VALUES (1,2), (2,3), (1,-1);

[^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.