Make grid database type usage consistent with RowSetOps

[errael]

@prasanthreddy-git @bpangburn

About using JDBCType Enum

Goals/issues

• Consistent treatment of JDBCTypes between grid and RowSetOps.
• Handling of java objects, currently RowSetOps works only with strings. (I think)
• Follow JDBC spec (noticed some non-compliance in RowSetOps); mostly because FLOAT is Double, REAL is Float.

In SSTableModel there are several places where's there's a TODO comment about using JDBCType. I think those comments were already there from way back, before this Grid PR.

This PR changes a simple case: getColumnClass modified using RowSetOps methods. findJavaTypeClass() handles more types that Grid was using, and some are handled differently:

• FLOAT returns Double.class
• NUMERIC/DECIMAL return BigDecimal.class
• More time related types handled
• More string types handled
• default is an exception instead of Object.class

Take a look, if it makes sense, other places can be modified to match. I'm unclear about the type mapping and/or how it interacts with the Grid. An additional issue, in SSDataGrid there working on an object and casting it to a specific type; that's currently not in RowSetOps. In RowSetOps it's mostly working with a string. Maybe working with objects needs to be put into RowSetOps.

[errael]

In RowSetOps add method updateColumnObject which updates a RowSet column with a value. There are actually two versions of this method, one just simple does rowSet.updateObject() and lets the jdbc driver do the conversion.

[errael]

@bpangburn For RowSetOps, AFAICT, this is good for review. Includes fixes

• better support TIMESTAMP
• TIME was added