Improve startup error from runDbCheck

Previously we would fail with a generic message suggesting to run
`gargantext-init`, but that wouldn't always be the case; sometimes
there might be problems connecting to the database, and we want to
show the raw exception. This code should help diagnosing what's wrong.

It also changes the error hint to report the correct executable, as
these days we use `gargantext-cli init` instead.