[Performance] Implement DB connection pool to wrap go-sqlcipher connection

[alexjba]

Description

Context: The current go-sqlcipher implementation does not support async read/write. This means that both reading and writing are blocking operations.

The goal of this task is to create a DB connection pool and delegate DB operations to different connections based on availability.

Pool configuration (based on these findings #10611):

1. write operations can be done on a dedicated connection (to avoid database is locked or table is locked errors)
2. The most efficient connection pool size is 10

[osmaczko]

Should we close this one in favor of status-im/status-go#3507 ?

[alexjba]

Closing in favour of status-im/status-go#3507