Mark base schema as invalid if init fails #46
Description
If there are any issues with the init procedure, we list the problems, but if that is skipped by the user and they restart the tool, the base schema exists, but our special comment is missing, and users get this error: "Base schema exists but missing which project ...."
It would be good to set a comment even after failed init that would explicitly tell us that init failed, so the next time the tool is restarted, we can give user the correct error message. (Maybe it would be good to also run the "create_changeset_dr" comparison again to show the unwanted differences.)
As a bonus point, when the "create_changeset_dr" is returning non-empty changeset, that may be a long output in console, and users may not see the original error message before the diff. So it may be good to rearrange things so that we first output the diff and at the end we raise one-line error which would make it clear things went wrong.