Fixed "Unable to update nested relation" errors when rolling back migrations

no issue

- we recently started wrapping rollbacks in transactions (https://github.com/TryGhost/knex-migrator/pull/161)
- in a number of migrations we were calling `model.destroy()` without passing through the options which includes the current transaction
- for models which are using `bookshelf-relations` this could result in an internal `SQLITE_BUSY: database is locked` error because it tries to run queries against tables that have been locked by previous queries in the transaction
- by passing through the options when calling `.destroy()` it allows the `bookshelf-relations` to re-use the same transction avoiding the database lock problems

core/server/data/migrations/versions/2.2/3-insert-admin-integration-role.js

@@ -53,7 +53,7 @@ _private.removeApiKeyPermissionsAndRole = (options) => {
                 return;
             }
 
-            return role.destroy().then(() => {
+            return role.destroy(options).then(() => {
                 logging.info(message);
             });
         });

core/server/data/migrations/versions/2.27/1-insert-ghost-db-backup-role.js

@@ -53,7 +53,7 @@ _private.removeApiKeyPermissionsAndRole = (options) => {
                 return;
             }
 
-            return role.destroy().then(() => {
+            return role.destroy(options).then(() => {
                 logging.info(message);
             });
         });

core/server/data/migrations/versions/2.27/2-insert-db-backup-integration.js

@@ -40,7 +40,7 @@ _private.removeGhostBackupIntegration = (options) => {
                 return;
             }
 
-            return integration.destroy().then(() => {
+            return integration.destroy(options).then(() => {
                 logging.info(message);
             });
         });

core/server/data/migrations/versions/2.28/4-insert-scheduler-integration.js

@@ -40,7 +40,7 @@ _private.removeGhostSchedulerIntegration = (options) => {
                 return;
             }
 
-            return integration.destroy().then(() => {
+            return integration.destroy(options).then(() => {
                 logging.info(message);
             });
         });