Hang on shutdown when large batches of session command are pending

If a client is repeatedly executing commands that get routed to all of the backend and one of the backends is slower to process the responses, the execution of a COM_CHANGE_USER will cause the session to remain alive until all the pending commands and the COM_CHANGE_USER has been completed. This has the effect of causing a hang on shutdown if MaxScale is stopped when this is ongoing.