refactor: r/demo/users

[leohhhn]

Description

Addresses: #2827

This PR refactors the current r/demo/users & r/sys/users system in accordance to the issue mentioned above. Below is the high-level overview of the new system.

It also makes a small change to the p/demo/releases lib.

r/gnoland/users/v1

• Fully replaces r/demo/users
• Is the main entry point for users looking to register a name, create an alias (rename themselves), or delete their username
• Implements allowed username pattern checks as per the issue r/sys/users Mainnet v1 (mvp) & v2 #2827
• Is pausable by GovDAO, contains no other administration functionality
• Contains a nice UI/render for users (please suggest improvements) - see bottom
• Uses r/demo/profile for displaying extra information about a user (to be moved to r/nt/profiles or r/gnoland/profiles)
• @jaekwon's request: add payment in GNOT for registration ✅

r/sys/users

• Namespace check moved to r/sys/names
• Contains the address/name <> user stores, to which only whitelisted realms can write
• Contains resolver functions & other useful getters
• Is callable only by whitelisted realms, such as r/gnoland/users/v1, etc.
• Whitelist is fully managed by GovDAO (after chore: remove govdao dependency in r/gov/dao/bridge #3523 was resolved)

r/sys/names

• Namespace checking functionality moved here (from r/sys/users), added tests, as discussed with @moul
• Verify function now only upgradeable with a GovDAO prop instead of previously being ownable
• Verify functionality is now not pausable and on by default, as per discussions with @moul. This means Portal Loop will need to be patched upon merging this PR, as many txs will fail due to not having proper namespace permissions. The namespace verify functionality is off by default, but should be enabled in genesis via r/sys/names.Enable(). The Portal Loop will indeed need to be patched if we enable this functionality.

Keeper & genesis params

• Updated the VM keeper to call r/sys/names for the namespace check instead of r/sys/users
• Updated params to load r/sys/names, which the keeper will call

r/gnoland/users/v1

r/gnoland/users

Currently this is the "releases" page for the user registration systems (example data):

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[leohhhn]

@zivkovicmilos @moul

Would you like to provide any preliminary feedback on the API before I go on renaming everything in the examples folder?

P.S. sorry about the force push, I messed something up with git.

[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)
🟢 Changes to 'docs' folder must be reviewed/authored by at least one devrel and one tech-staff
🟢 Pending initial approval by a review team member, or review from tech-staff

☑️ 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: leohhhn/gno)

Then

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

Changes to 'docs' folder must be reviewed/authored by at least one devrel and one tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 A changed file matches this pattern: ^docs/ (filename: docs/concepts/namespaces.md)

Then

🟢 Requirement satisfied
└── 🟢 And
    ├── 🟢 Or
    │   ├── 🔴 Pull request author is a member of the team: tech-staff
    │   └── 🟢 At least 1 user(s) of the team tech-staff reviewed pull request(with state "APPROVED")
    └── 🟢 Or
        ├── 🟢 Pull request author is a member of the team: devrels
        └── 🔴 At least 1 user(s) of the team devrels reviewed pull request(with state "APPROVED")

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🟢 Requirement satisfied
└── 🟢 If
    ├── 🟢 Condition
    │   └── 🟢 Or
    │       ├── 🟢 At least 1 user(s) of the organization reviewed the pull request (with state "APPROVED")
    │       ├── 🟢 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🟢 Then
        └── 🟢 Not (🔴 This label is applied to pull request: review/triage-pending)

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

[leohhhn]

@moul

Added FIFO to the rendering of gnoland/users/v1. Only thing left now is this:
#3166 (comment)

Also, let's see how we're going to patch the Portal Loop for this 🙏