fix(DoubleColumnType): correctly handle precision when casting Float to DoubleColumnType for a `real` column

[jackgisel-RL]

we found an issue when casting values from the DB to a DoubleColumnType when the underlying column was a real

isolated example

Problem

Solution

bug found in prod

db had this:

when debugging through the value was represented as a Float, shown here:

the data is coming back as Float because the Postgres column is a real and not a double precision