refactor(examples): use std.Address based behaviour

[r3v4s]

Description

To make contracts more simpler(and low computation for execution), it is better for contract to manipulate with only std.Address rather than using users.AddressOrName and resolving it. (Discussed with @moul)

Clients such as gnoeky, gnoweb or adena should perform look up(convert username to address) and pass address value to contract.

[Gno2D2]

🛠 PR Checks Summary

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

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)
🟢 Pending initial approval by a review team member (and label matches review triage state)

☑️ 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
└── 🟢 The pull request was created from a fork (head branch repo: gnoswap-labs/gno)

Then

🔴 Requirement not satisfied
└── 🔴 Maintainer can modify this pull request

Pending initial approval by a review team member (and label matches review triage state)

If

🟢 Condition met
└── 🟢 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 approved the 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]

Just a heads up: I also made this change in #3166 - you'll want to check out the API of r/sys/users, primarily the users.gno file. It's mostly final

[leohhhn]

@r3v4s can you check the bot which is making the CI red? And we can merge after

[notJoon]

Please enable the "Allow edits from maintainers" option to fix CI fail.

[r3v4s]

@leohhhn
CI failing because of Allow edits and access to secrets by maintainers.
@notJoon and I really couldn't find this option on our side T.T

[n0izn0iz]

There was a request to open PRs from our personal forks to address this, not sure you can/should enable this at your org level

[leohhhn]

Clicked "ignore" on the bot because the last requirement seems to be a bug on github. Pr looks good.

[leohhhn]

Changes were only in the examples folder, but CI didn't run txtar tests on this change breaking master. Fixing: #3590