Avoid knex warning when destroying a user

no issue

- the warning is "Transaction was already complete"
- destroying a user happens in a transaction, but the event is not asynchronous
  - so we have to ensure that we don't operate on a finished transaction

core/server/models/base/listeners.js

@@ -31,9 +31,9 @@ common.events.on('user.deactivated', function (userModel, options) {
         return;
     }
 
-    models.Accesstoken.destroyByUser(options)
+    models.Accesstoken.destroyByUser(_.omit(options, 'transacting'))
         .then(function () {
-            return models.Refreshtoken.destroyByUser(options);
+            return models.Refreshtoken.destroyByUser(_.omit(options, 'transacting'));
         })
         .catch(function (err) {
             common.logging.error(new common.errors.GhostError({