update typeAliases

[JLDLaughlin]

A user surfaced the following Metabase error (using our pgjdbc fork):

03-05 17:03:44 ERROR sync.util :: Error syncing Fields for Table X: Unable to find type name for double precision
("io.materialize.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:206)"
 "io.materialize.jdbc.PgDatabaseMetaData.getColumns(PgDatabaseMetaData.java:1503)"
 "com.mchange.v2.c3p0.impl.NewProxyDatabaseMetaData.getColumns(NewProxyDatabaseMetaData.java:3140)"
 "--> driver.sql_jdbc.sync$describe_table_fields.invokeStatic(sync.clj:152)"
 "driver.sql_jdbc.sync$describe_table_fields.doInvoke(sync.clj:149)"
 "driver.sql_jdbc.sync$describe_table.invokeStatic(sync.clj:198)"

It turns out our typeAliases info didn't include all of the available aliases for Materialize's built-in types.

[quodlibetor]

these (json/jsonb) aren't technically identical but they should behave similarly enough for metabase purposes so it's probably fine?

[JLDLaughlin]

yeah--it's definitely sort of weird! but we do technically list it as an alias here.

[JLDLaughlin]

For posterity, I tested this locally by:

1. Building the updated pgjdbc jar
2. Rebuilding the metabase-materialize-driver
3. Spinning up Materialize & Metabase
4. Creating the following view in my materialized instance: create view viewy as select 1::double precision as col;
5. Making sure I could SELECT col FROM viewy and SELECT col::double precision FROM viewy

[JLDLaughlin]

I needed to make this change to build the jar locally!