feat(examples): add disperse

[leohhhn]

Description

This PR adds a port of the Disperse.app smart contract on EVM. It helps showcase how sending GNOT to and from a realm works.

This PR is part of the Dogfooding initiative. Here is the linking comment.

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

All modified and coverable lines are covered by tests ✅

Comparison is base (05dccce) 56.26% compared to head (9079f54) 56.26%.
Report is 5 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1414   +/-   ##
=======================================
  Coverage   56.26%   56.26%           
=======================================
  Files         425      425           
  Lines       64408    64408           
=======================================
  Hits        36237    36237           
  Misses      25349    25349           
  Partials     2822     2822           

Flag	Coverage Δ
go-1.21.x	∅ <ø> (∅)
misc	∅ <ø> (∅)
misc-_test.genstd	∅ <ø> (∅)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[leohhhn]

This PR is currently blocked by the inability to write tests:

• gno test does not work correctly with the banker API (a larger issue)
• txtar tests do not currently provide enough configuration - for testing the Disperse app, there needs to be multiple accessible addresses within the testing context, and currently the only accessible one is test1.

@moul @thehowl @deelawn @zivkovicmilos - how can we progress on making the testing experience better?

[zivkovicmilos]

This PR is currently blocked by the inability to write tests:

• gno test does not work correctly with the banker API (a larger issue)
• txtar tests do not currently provide enough configuration - for testing the Disperse app, there needs to be multiple accessible addresses within the testing context, and currently the only accessible one is test1.

@moul @thehowl @deelawn @zivkovicmilos - how can we progress on making the testing experience better?

I'm not sure what the exact problem is with using txtar for an e2e test. What kind of data do you need in the test?

[thehowl]

• txtar tests do not currently provide enough configuration - for testing the Disperse app, there needs to be multiple accessible addresses within the testing context, and currently the only accessible one is test1.

Two proposals:

1. Adding proper support for adding a key to the keystore, ie. being able to call gnokey add and pass in the mnemonic in txtar. (Reqires changing txtar up a bit)
2. Using gnokey import/export (I think this can be done now already)

[thehowl]

One more thing: it seems to me that you don't actually need to create the accounts you claim you need to create (from the current state of the code).

That is, unless they need to be able to move coins on their own, the accounts don't need to have a matching private key.

You can just use disperse to send off tokens to some account strings you made up, and then check the txtar result of doing gnokey query auth/accounts/%s.

[leohhhn]

Update on this: this has been sitting for a ton of time. Will get back to it soon hopefully, it's not a priority right now.