feat: improve gnodev logging

[gfanton]

This PR enhances the gnodev logger for easier debugging:

• Use charm log for better logging and improved display
• Include a way to manage genesis delivery transactions result during initialisation using a custom handler in gnoland. This is currently the only way I've found to manually handle errors. Refer to this commit for more details: ecd1109
• Enhance column display
• Stack can be available if --verbose is specified

Contributors' checklist...

• Added new tests, or not needed, or not feasible
• Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory
• Updated the official documentation or not needed
• No breaking changes were made, or a BREAKING CHANGE: xxx message was included in the description
• Added references to related issues and PRs
• Provided any useful hints for running manual tests
• Added new benchmarks to generated graphs, if any. More info here.

[zivkovicmilos]

@gfanton
What is the status of this PR?

[gfanton]

@zivkovicmilos
I was waiting for feedback on the error display. I will make some slight adjustments, and then it will be ready for review.

[codecov]

Codecov Report

Attention: Patch coverage is 16.00000% with 21 lines in your changes are missing coverage. Please review.

Project coverage is 45.07%. Comparing base (2a9a8f5) to head (4a6baa4).
Report is 3 commits behind head on master.

Files	Patch %	Lines
gno.land/pkg/gnoland/app.go	0.00%	13 Missing ⚠️
gno.land/pkg/gnoland/node_inmemory.go	0.00%	8 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1790      +/-   ##
==========================================
- Coverage   45.08%   45.07%   -0.01%     
==========================================
  Files         464      464              
  Lines       68014    68023       +9     
==========================================
- Hits        30661    30660       -1     
- Misses      34778    34786       +8     
- Partials     2575     2577       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[leohhhn]

Hey, I played around with this a little. I recorded looms (sorry for two - got cut off):
Loom 1
Loom 2

Seems that genesis TX loading is not working properly and reloading the state is failing for some reason (ungracefully). See the looms, and lets discuss, not fully sure what's up.

EDIT:

OK, I think I figured out what the issue is. Monorepo I used to install this already has a p/demo/memeland & r/demo/memeland package & realm, and I was trying to load in the package with the same path. How can we handle this error better?

EDIT2: Yup, can confirm that the above was the issue. Can we handle this edge case? Check already deployed packages against the gno.mods you're trying to run with gnodev, and error out?

Also, the genesis TXs still aren't being loaded - seems like a separate issue.

[gfanton]

@leohhhn Wow! Good catch, thanks! I believe Genesis TX FIle shouldn't load by default during development. It could be loaded with a separate flag, making it a feature rather than an issue 😛. As for the other bug, I'm unsure about the best approach. I'm concerned that overriding a package for the user might cause unexpected behavior. I suggest providing a clear error message for duplicate packages and a flag(?) for users to explicitly override the package.
In any case, could you open two issues for this? It's not related to this PR. The genesis I load in gnodev is a crafted one with all the added packages (not the file from the monorepo). What I did in this PR is add a way to manually handle errors when delivering transactions from the genesis. This allows me to properly handle and display errors in gnodev.

[zivkovicmilos]

It could be loaded with a separate flag, making it a feature rather than an issue 😛

I'm glad you brought that up: #1883 😎

[zivkovicmilos]

Love this, now we have a reference implementation 💯

[leohhhn]

Thank you for figuring out what the issue was with the panic when exiting or invalid syntax (it turned out to be that I was using Go 1.21 and for some reason it was failing).

Let's tackle other issues and possible improvements I mentioned after merging this 🙏

[leohhhn]

@gfanton is this good to merge?

[gfanton]

@leohhhn I was waiting for potential additional reviews, but i guess we can merge it now