Don't run migrations for every test #2167
Description
Right now our test suite runs migrations for every test (ensuring the tests is working on a clean DB state / avoiding contamination across tests). A faster way to achieve this would be to have the suite run migrations once at the start of running tests, store the resulting database state into a loadable format, and re-load that state directly for each test.