Introduce SPI Row/Tuple converter

#### Describe the feature

Add new convention method for `Row` to accept `converter`.
Introduce 2 converter interfaces, it should be 2-way converter: `JDBC`/`Reactive SQL` <=> User data type.
- `DataTypeConverter` for converting by data type
- `ColumnConverter` for converting by data type and column name

Something like that
```java
interface Row {
default T get(String column, ColumnConverter converter) {
return converter.convert(getValue(column));
}
}
```

Then extract every `get` to `Converter`, then add them to `SPI` as Vertx convention.
On each database driver/business model, developer can easy enhance or override default converter and make seamlessly UDT from database to java type

The concept will be similar on what I have done in [jooqx](https://github.com/zero88/jooqx) such as:
https://github.com/zero88/jooqx/blob/fcc473908cdbcc7b61544ccfbc97b4f7a8797b13/core/src/main/java/io/zero88/jooqx/datatype/JooqxConverter.java#L19
and
https://github.com/zero88/jooqx/blob/fcc473908cdbcc7b61544ccfbc97b4f7a8797b13/core/src/main/java/io/zero88/jooqx/datatype/DataTypeMapperRegistry.java#L23

#### Contribute
I might take it if you want to minimum API change in my lib also.