LockManager invalidations queue may grow and use all memory

In a cluster setting, the LockManager holds a JDBCMapper with an associated InvalidationsQueue, which queues all invalidations for the cluster. But the LockManager never flushes this queue (which it doesn't need as the mapper doesn't use the invalidations, the mapper is used purely for SQL generation).

This mapper shouldn't have a queue for invalidations at all.