feat: add r/grc20reg

[moul]

Depends on #2743
Continues #1072
Related #1275, #1262
Depends on #1257
Depends on #2551
Alternative to #3135

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.78%. Comparing base (a1a7cb3) to head (81fdbcf).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2516      +/-   ##
==========================================
- Coverage   63.79%   63.78%   -0.01%     
==========================================
  Files         549      549              
  Lines       78819    78781      -38     
==========================================
- Hits        50281    50254      -27     
+ Misses      25146    25140       -6     
+ Partials     3392     3387       -5     

Flag	Coverage Δ
contribs/gnodev	61.16% <ø> (ø)
contribs/gnofaucet	14.82% <ø> (ø)
misc/genstd	79.72% <ø> (ø)
tm2	62.34% <ø> (-0.01%)	⬇️

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.

[moul]

Blocked by #2743

[r3v4s]

First of all, I know that this pr is sill working in progress, but couldn't wait for charming of supporting multiple grc20 tokens by default in gno-eco system(in this case grc20reg) and did some test.

Currently, grc20reg takes object from other realm to register it, and it seems like affects stack-frame. (tested with _test.gno)

On the other hand, testing with txtar slightly returns different result, cannot modify external-realm or non-realm object.
Is this due to #2743 you mentioned blocked by ??

[moul]

Yes, this grc20reg is no longer a work in progress, but it depends on the changes in the PR, specifically those in #2743.

For a preview of fully working examples, you can check my meta PR #2551, which includes some VM fixes, this completed realm, and other realms that use it, such as the atomicswap realm, for instance.