Authentication data should be thread specific

Currently the authentication data is stored in a sqlite database that is opened in serialized mode. If clients connect and disconnect in rapid fashion this will cause contention between the worker threads, which will degrade the overall performance.

Instead, each thread should maintain its own database of authentication data, so that the user authentication causes no cross-thread interaction. The data need not be persisted as the user data is anyway always refreshed when MaxScale starts.