Numeric versus character column type conflicts

When two mappings, or the mapping and the reflected database column, disagreed on an incompatible column type, previous releases failed with a -bad-colMetaDataException (or logged a warning with disableSchemaFactoryColumnTypeErrors). Conflicts between numeric and character types are now silently resolved to VARCHAR, and values are converted on read and write. As a side effect, SynchronizeMappings=validate and SchemaManager.validate() no longer report numeric versus VARCHAR drift; verify such columns manually. All other incompatible combinations still fail as before.