Gnodev to give useful info about failing replays

[moul]

Gnodev can sometimes replay transactions and sometimes cannot. We should optimize this information for readability when used locally by developers.

Another important need for this feature is to enhance the failing report for portal loops. This will allow us and any other loop to update their gnoland deps (binary, examples/ folder, etc) while maintaining a clear list of issues related to failed transactions.

Developers will then have the option to ignore the warnings or address them.

In our specific case as portal loop maintainers, we want to create a simple process where a PR can be merged even if it breaks the loop (a.k.a, no CI). However, we also need meaningful logs to assist us in "patching" the history.

The use cases I have in mind are:

• Simple patching, like #2865
• Massive breaking changes, such as #2425, where we would like to fix numerous transactions.

Related with #2866
See #2862 (comment)