Synchronous token pool activation causes database deadlock

[awrichar]

#460 added the ability for fftokens connectors to return a synchronous 200 response to both /createpool and /activatepool, rather than a 202 followed by a websocket event. However, returning 200 from /activatepool causes FireFly to deadlock by trying to start a new database transaction (via RunAsGroup) while another one is already open.