WIP feat(examples): add p/moul/pageable

[moul]

• Add generic p/moul/pageable
• Refactor p/demo/avl/pager
• Add p/moul/ulist/pager
• Add some wrappers around slices (and maps?)
• Think more about alternatives, like "cursors" instead of "offsets"

Depends on #3407

[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
└── 🟢 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

[n2p5]

I know this is still in draft, but I took a look over the code and it is looking really nice. I put in a couple of notes and pointed out one place that you could avoid type conversions with a fun math trick. Let me know when its out of draft. I like this structure a lot.

[n2p5]

I really like this breakdown in functionality, very clear to the reader.

[n2p5]

do we have a preference for interface{} vs any? It feels like any is a nice shorthand in general.

[n2p5]

This can be more simply implemented as

totalPages = (totalItems + pageSize - 1) / pageSize

This avoids the need for type conversions.