Better handling of the table initialization

[goetas]

Q	A
Type	improvement
BC Break	-
Fixed issues	#935

Summary

This PR solves #935.

The idea behind is that:

• if there is no migration table then we consider it as if there are no executed migrations (in this case all the read command work as usual, the write command will create the table as expected on the very first migrations run)
• if there is a table but is not up to date, any command will trigger an exception and the user will have to run the sync-metadata command

With this PR the read commands will never update your DB and the write commands will do so only after the user's consent