Queue.take in SQLPool can produce deadlock

Describe the Bug
In SQLPool we use take on the queue to wait for a connection to become available. If no connections become available (for example if a single thread is using up all connections) it produces a deadlock causing a lockup of the entire application since all database queries will run into a deadlock

To Reproduce
Steps to reproduce the behavior:

1. Set the pool size to 1
2. Call get once
3. Call get a second time -> gets stuck

Expected behavior
The pool should use poll instead and throw an Exception after a reasonable amount of waiting time preventing a lockup of the entire application

Environment Information:

• Java Language Level 8
• Version 1.0.3

Additional Context
The root cause of this might be a different issue since the pool shouldn't have ran out of connections in the first place. We can check this issue once proper exceptions are thrown.

Empieza en la ruta de SQLPool que usa Queue.take y luego reproduce el problema con un pool de tamaño 1 llamando a get dos veces. Compara el comportamiento de bloqueo actual con la espera temporizada y la excepción esperadas, y verifica que la aplicación ya no se quede atascada cuando no haya ninguna conexión disponible.