WIP feat(gno.land): account sessions support (exploration 1)

[moul]

• high-level changes (structs, interfaces)
• pseudo code for vmkeeper changes
• pseudo code for sdk changes
• think about
  • storage efficiency
  • lookup efficiency
  • reusing a "burned" address (especially the initial one that can be derived to the same std.Address)
  • ...
• give context on what I considered, why i chose this direction etc
• explain how i envision gnokey mobile, playground on ipad or web-first, mix with native apps, airgap txs, airgap session management; deep links, qr code, link that we can share in chat apps; "gnoboards" working with "gnokey" on mobile; creating temporary accounts -> directions for the berty team + "cross-wallet initiatives"
• explain how we could mix session management with tx for one-shot txs, like one-shot session usages

random personal notes (tmp):

• tm2
• subaccount
• gnoaccount
• managed by contract <3
• wallet connect; qr code; patterns; steps
• works for teams r/sys/teams
• onbloc, berty, alex
• UX: cookies, "manage devices"
• self-expiring sessions (cookies)
• key rotation
• validator limited key

Related with #1499

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: moul/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission