Handle invalid numeric values in JDBC source

[sherifnada]

What

NaN and infinity are not supported in JSON schema, but are allowed values in various Postgres numeric types . So we force them into null at the DB level.

Releasing this now to fix a bug that a user is having. But we'll want to have tests like this for every data type's edge cases. This is coming in a later PR.

[michel-tricot]

I am afraid that this is adding transformation logic to the source. What would be another option?

[jrhizor]

It's unfortunate that NaN/null/infinity will look the same on the destination, but I can't think of a better way right now.

This behavior should be added to our data types documentation.