Improve Clarity of Error Messages for Version Mismatches

[notJoon]

Description

If a previously installed gno with make does not match the current version, it panics with nil pointer error (actually, I don't know the exact conditions under which this happens). This message is not very helpful in indentifying the cause of the issue, making it challenging to trace and resolve the problem.

Therefore, I think improving the errorr message is important for easier problem-solving.

Note: I solved this problem by running make install.

[thehowl]

There are many reasons that this could happen and it essentially doesn't matter right now. The simple answer is we're updating crucial parts of the code so often that old binaries with new files (like new stdlibs, or running gno.land with an old directory for the blockchain data) will just break all the time.

For the gno command, implementing #1248 will fix many problems already, by not requiring users to have a root dir and as such not creating "incompatibilities".

For gno.land, I think the real answer is "tough shit" for now. I don't think it makes sense to append to all of our error messages "are you running the latest version? did you run make fclean in gno.land?`. It does make sense to have this as the no. 1 troubleshooting help in CONTRIBUTING and/or docs. cc/ @gnolang/devrels.

[leohhhn]

Hey @notJoon, thanks for pointing this out. Gno.land generally has bad error handling at this point in time, unfortunately.
We're working on the developer experience, including the docs and hopefully this will ease the builder path.

If you see any place where you can contribute to fixing this issue, please do so, as you know any help is much appreciated :)