feat(examples): add p/moul/udao/... packages

[moul]

I had this idea when I saw everyone trying to create DAO interfaces for managing members and voting.

I believe we should focus on a DAO that operates independently of member and vote management. Instead, it should handle proposals with an internal implementation that can remain private.

My two main goals for this are:

1. Composable DAOs, where a proposal can draw 60% of its power from DAO A and 40% from DAO B. This allows both DAOs to manage their internal implementations as they see fit.
2. Interchain DAOs, where you can focus on top-level metrics without worrying about internal details.

I'm looking for feedback. My goal is to see a variety of DAO implementations in the ecosystem, such as the ones from Teritori and Gno.me, while ensuring they can be rich in features yet still implement a minimal interface.

udao could provide both the minimal interfaces and the necessary helpers.

cc @gnolang/devx @gnolang/teritori

Depends on #3400 (cherry-picked)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[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