Alternative design: update the `DatabaseClient.execute...` APIs to take statement creation functions/lambdas instead and wrap the whole process in a `suspendTransaction`

This would make both the APIs and implementations simpler if it doesn't impact performance.

- Blocking `transaction` wouldn't work for this because the `statement` arg needs to be suspend for Vert.x SQL Client calls.
- Benchmark the performance impact with TFB first.