feat: add r/moul/present

[moul]

This realm is a good example of reusing and integrating some of my recently added libraries:

• p/moul/md feat: add p/moul/{md,debug,web25} + update r/moul/home #2819
• p/moul/mdtable feat: add p/moul/mdtable #3100
• p/moul/realmpath feat: add p/moul/realmpath #3257
• p/moul/txlink chore: refactor txlink in order to extend it #3289
• p/moul/collection feat(examples): add p/moul/collection #3321
• p/demo/avl/pager feat: add p/avl/pager #2584

It helped me identify that txlink was not escaping the arguments, which resulted in invalid links. (fixed in #3682)

Additionally, it provided me with a better understanding of:

• The shortcomings of the p/moul/md API, particularly regarding "\n" handling
• The need for improved management of the pager for p/moul/collection
• What kind of UI improvements we could need on gnoweb. META Gnoweb UI Improvements #3355

Demo:

CleanShot.2025-02-03.at.21.26.46.mp4

I also suggest you to look at the filetest.gno file.

I believe we should proceed with the merge, to inspire others to create similar composed realms.

However, I have a few improvement ideas:

1. Extract most of the generic logic into a p/moul/present.
2. Consider either making r/moul/present importable by r/coreteam/present to create a hub for presentations from all teammates, or the opposite: make r/coreteam/present the content source and allow r/moul/present to display a subset where author="moul" What are your thoughts?
3. Clean up the code using an improved p/moul/md and possibly new p/ generic utilities.

Depenes on #3682

[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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!