`serve`: refactor the `Blockchain failed to start.` error message

[lumtis]

When the blockchain fails to start, because of any reason (wrong gentx, broken logic, incorrect staking token), the following message appear (when -v is not used):

Blockchain failed to start.
If the new code is no longer compatible with the saved state, you can reset the database by launching: starport chain serve --reset-once

This message may be a bit ambiguous because most of the time people starting development with Starport may think the statement If the new code is no longer compatible with the saved state is true and therefore try to debug the wrong problem

We may need to show the underlying error even when -v is not used or give indication to the user to run the command with -v

[Jack-Above]

I was in this exact situation... non-verbose logging output made me search for a solution to the wrong problem

[Starblue0]

Did you figure it out yet? Just wondering

[blarsy]

+1 I'd love having been reminded of the existence of the -v switch in the "Blockchain failed to start." error message.