JsonType should use the actual JDBC type, not OTHER

On some DBs there's no native JSON type. So we have to use a VARCHAR, but still map it to the new "org.apache.cayenne.value.Json". This causes exceptions (at least I saw it on Derby). To fix it, all the JsonType methods that hardcode Types.OTHER should pass the actual type to JDBC. It is available as a method parameter