fix #5519

🦥 In Progress

select:
SELECT *
FROM X WHERE col1 IN ?;

I think the only place in SqlDelight that generates Sql at runtime is to expand var args to IN (?, ?,...)

🛞 The Driver and Dialect are responsible for any specific implementation of runtime argument binding
⚡ Transacter feels like the wrong place for generating runtime sql. Keep existing createArguments as there is a lot of test code generated and instead forward to the Driver implementation
🚨 MySql/MariaDb R2dbc uses ? and PostgreSql R2dbc uses $1, $2 ... makes it difficult to determine the argument binding needed as we need to know the dialect and driver

• Adds createArguments is part of Driver/Dialect behaviour - PostgreSql native R2dbc has specific bind argument and reference by position and index. If you were manually using the driver to execute sql then createArguments should be part of that
• Add default implementation for ? binding
• Update Transacter.createArguments forward to Driver.createArguments so there is no change to compiled code
• Update SqlDriver for runtime.api and android.api and jdbc.api
• Add class PostgresqlR2dbcDriver to override createArguments for special case
  • Currently uses delegation as a SqlDriver unless we really need it then could open and inherit from R2dbcDriver
• Add async integration test for var arg binding using IN ?

Example client use

suspend fun getAsyncSqlDriver(): SqlDriver {
    val connectionFactory = getR2dbcConnectionFactory()
    return PostgreSqlR2dbcDriver(connectionFactory.create().awaitFirst())
}

Note: This is different than the fix for #5319 where the expansion of INSERT VALUES var args can be known at compile time.