False-positive detection of changes in existing coreschema file (V1)

[vanstyn]

The current built-in CoreSchema version is still at V1, so there are no deployment/migration scripts yet to handle upgrading existing coreschema database files. But, as a preliminary measure, the system does already attempt to verify that existing coreschemas do match the current schema by doing an md5 check on the deployment_statements.

This was already planned to be temporary, however, it is already causing problems because it is too sensitive. Any changes, including whitespace, quoting, etc, show up as changes which is a fatal exception (and, in fact, the external SQLT/Deployment stuff has recently tweaked the DDL it generates, which is what made this a short-term problem)

Issue with RapidApp v0.99102

[vanstyn]

Fixed as of v0.99200 (a295b62a)