The affected database role test uses a static name for the role name. It's possible for two parallel runs to collide and attempt to drop/create the same role at the same time, causing the test to fail.
The affected database role is granted future permissions on all tables in the database, which affects other grants tests.
Solution
Add a semi-unique suffix to the role name (1 in 1MM chance of collision now)
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
Problem
The affected database role test uses a static name for the role name. It's possible for two parallel runs to collide and attempt to drop/create the same role at the same time, causing the test to fail.
The affected database role is granted future permissions on all tables in the database, which affects other grants tests.
Solution
Checklist