feat: Implement ./contribs/gnodev command

[gfanton]

Introducing gnodev Command

This PR introduces the gnodev command, designed to facilitate the development and iteration of realms package. Its primary role is to operate an in-memory node along a gnoweb server.

Key features of this command include:

• Recursive Monitoring: It continuously monitors the example packages folder for any file changes. Moreover, it offers the flexibility for users to monitor and add directories outside the example folder by specifying them as arguments.

• Dynamic File Change Response: When a file change is detected, gnodev endeavors to reload the affected package and restart the node. In an effort to maintain the current state, it will try to reapply all previous blocks.

• Interactive Controls: Users have the ability to reload the node at any moment by pressing R and can reset the current node state using Ctrl+R.

• Command Flags:

  • The -minimal flag, which prevents the node from loading the example folder.
  • The -no-watch flag, used to disable the automatic file change monitoring feature.

Additionally, any raw arguments passed to the command will be considered as packages path and will be loaded into the node.

ref: #1174

GnoWeb package

This PR also introduce GnoWeb package since it's now running in gnoweb and gnodev command.

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.

[codecov]

Codecov Report

Attention: 167 lines in your changes are missing coverage. Please review.

Comparison is base (eef0c98) 56.32% compared to head (5173c05) 56.30%.

Files	Patch %	Lines
gno.land/pkg/gnoweb/gnoweb.go	62.76%	125 Missing and 18 partials ⚠️
gno.land/pkg/gnoland/node_inmemory.go	0.00%	21 Missing ⚠️
gno.land/pkg/gnoland/genesis.go	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1386      +/-   ##
==========================================
- Coverage   56.32%   56.30%   -0.02%     
==========================================
  Files         422      422              
  Lines       65699    65699              
==========================================
- Hits        37003    36993      -10     
- Misses      25815    25821       +6     
- Partials     2881     2885       +4     

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

[moul]

I love this PR and recommend gathering community feedback and iterating on it.

It would be helpful to move most of the new logic to contribs/ and create a separate go.mod file. This enables further optimizations while keeping gnovm and gno.land minimalistic.

After moving to contribs/, we should thoroughly review the changes in gnovm/ and gno.land/, and perform a light round of checks on the contribs/ folder before merging and iterating.

[gfanton]

@moul that's make perfect sense, I will move this to /contribs

[moul]

@zivkovicmilos @ajnavarro, just wanted to let you know that we encountered a problem while importing tx-archive. It seems that tx-archive imports gno. I suggest we relocate all the tx-archive logic to this repository and reserve the tx-archive repository for specific purposes like releases, or delete it.

[zivkovicmilos]

@zivkovicmilos @ajnavarro, just wanted to let you know that we encountered a problem while importing tx-archive. It seems that tx-archive imports gno. I suggest we relocate all the tx-archive logic to this repository and reserve the tx-archive repository for specific purposes like releases, or delete it.

We'll consider opening a PR to migrate out both tx-archive and the faucet repo to their respective places in the gno repo, since they both utilize the main gno repo heavily.
@gfanton mentioned utilizing Go workspaces, so it should make our lives easier in the future in the monorepo