Orion migration tool failing on Orion DB path relative to a separate directory

[vmichalik]

A user was running the Orion migration tool in a different directory to Orion. Orion's config only included a relative DB path, so the Orion migration tool created a new empty DB that was not able to migrate.

Modifying orion.conf file to add storage and workdir parameters with absolute paths fixed the issue and made the migration possible.

Another way would have been to run the migration tool from the same place where Orion was running so they get the same default path.

Improving the documentation around this will help solve the problem, as recommended here: Consensys/doc.orion#70

Adding a clearer error message would help alert users to the problem.