Fix for 2647

Instead of basing on the contents of the Installation (since it changes during the upgrade process) use a boolean to determine whether the schema has been customized or not as return value of MigrationManager.isSchemaCustomized (in any case the method's javadoc already required MigrationManager.calculateSchemaCustomizations to be called so there is no change of behavior).