feat: add FOMO3D game implementation

[stefann-01]

This PR introduces FOMO3D, a blockchain-based game that combines lottery and investment mechanics, implemented as a Gno realm. The game creates an engaging economic model where players compete to be the last key purchaser while earning dividends from subsequent purchases.

Key Features

• Players purchase keys using GNOT tokens
• Each key purchase:
  • Extends the game timer
  • Increases key price by 1%
  • Makes buyer potential jackpot winner
  • Distributes dividends to existing key holders
• Automatic prize distribution:
  • 50% to jackpot (winner)
  • 30% as dividends to key holders
  • 20% to next round's starting pot
• Maximum game duration of ~24 hours
• Full test coverage

Technical Implementation

• Utilizes AVL tree for player data storage
• Implements dividend distribution system
• Includes comprehensive test suite
• Features markdown-formatted render functions for game state visualization

How to Use

1. Start game with StartGame()
2. Purchase keys with BuyKeys()
3. Claim dividends with ClaimDividends()
4. View game status via render functions
5. Winner automatically receives jackpot when timer expires

Testing

All core functionalities are covered by unit tests including:

• Full game flow
• Key purchasing mechanics
• Dividend distribution
• Game ending conditions

Inspired by the original Ethereum FOMO3D game but rebuilt for the Gno platform.

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)
• The pull request description provides enough details

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: stefann-01/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

The pull request description provides enough details

If

🟢 Condition met
└── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)

Can be checked by

• team core-contributors

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[leohhhn]

Might make sense to pack these into a struct, wdyt?