feat: add txlink builder and send special arg

[alexiscolin]

Related to #3919, this PR introduces a new streamlined way to build transaction links in gno, with built-in support for send values.

New Builder Pattern:

// Create transaction links with a fluent interface
txlink.NewLink("MyFunc").
    AddArg("key", "value").
    AddArgs("k1", "v1", "k2", "v2").
    SetSend("1000000ugnot").
    URL()

Added multiple ways to specify send values:

• Via builder pattern: SetSend("1000000ugnot")
• Via direct call: Call("MyFunc", ".send", "1000000ugnot")

The new builder pattern uses the same Realm logic as the previous one

• Support for current realm (relative paths)
• Support for local realm paths
• Support for fully qualified paths

Priority Rules:

As a refinement, implemented clear priority rules for send values:

• Last AddSend call wins

Test Coverage

Added comprehensive test suite covering:

• Basic builder functionality
• Realm handling
• URL encoding
• Send values (all methods)
• Empty/special values
• Error cases

[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)
🟢 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: alexiscolin/gno)

Then

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

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[moul]

I'm usually against this pattern, but in this specific case, it may be interesting to consider making the value any, and then trying to convert basic types to a string. wdyt?

Suggested change

	func (b *TxBuilder) AddArg(key, value string) *TxBuilder {
	func (b *TxBuilder) AddArg(key, value any) *TxBuilder {

[alexiscolin]

Yeah it's not recommended but but might be more flexible and easy to use. @leohhhn since you used this packages way more than me, do you think it could be helpful?

[leohhhn]

I'm more for typed approaches; pretty sure someone will try to jam in a struct or slice or other invalid input; we can have this approach when we also allow a pattern like std.Emit(&mystruct)

[leohhhn]

lgtm

[leohhhn]

Can you modify the render of r/gnoland/users/v1 to add the .send arg being 1 GNOT? Just for a testable example.