Investigate flaky CrossDatabaseModificationAcrossUnsupportedTablesError failures in master in `spec/features`
From this slack thread https://gitlab.slack.com/archives/C01TQ838Y3T/p1643192770158100 we see a bunch of flaky failures in master recently https://gitlab.com/gitlab-org/gitlab/-/issues?search=CrossDatabaseModificationAcrossUnsupportedTablesError&sort=created_date&state=opened&label_name[]=failure::flaky-test . Most likely this was introduced by !76717 (merged) .
All of the problems appear to be in spec/features
so perhaps there is something about how Capybara interacts with our implementation of TransactionStackTrackRecord
. Possibly wondering if Thread.current[:gitlab_transactions_stack]
might have issues in Capybara.