[Proposal/Ecosystem] Introducing gea-query: A Zero-Hooks data-fetching and caching library

Hi Gea team,

First of all, congratulations on the amazing framework. I deeply respect Gea's core philosophy—especially its pure OOP approach and explicit resource management (Zero-Hooks design). It feels incredibly clean and intuitive to work with.

To complement this philosophy, I have developed and just published a new library called `gea-query`.

- **Repository:** https://github.com/KoHaRxnP/gea-query
- **npm:** https://www.npmjs.com/package/gea-query

### What is gea-query?
It is a definitive data-fetching and caching library designed specifically for Gea. Traditional state management often relies heavily on hooks or implicit reactive bindings, which can break Gea's clean class-based structure.

`gea-query` solves this by introducing a Class Mixin approach (`withQuery`), allowing components to handle asynchronous data streams seamlessly while perfectly synchronizing with Gea's explicit `dispose()` lifecycle for safe resource cleanup.

### Key Features:
- **Class Mixin Integration:** Seamlessly injects query capabilities into Gea components without breaking the OOP architecture.
- **Smart Caching:** Built-in request deduplication and `staleTime`-based cache management.
- **Strict TypeScript Support:** Fully typed mixin constraints with comprehensive `.d.ts` generation.

### Proposal
I created this to help grow the Gea ecosystem and assist other developers facing data-fetching challenges in their Gea apps.

If it aligns with the project's direction, I would be honored if you could consider adding it to the official documentation (such as an "Ecosystem" or "Community Libraries" section). Of course, I would be more than happy to open a Pull Request for the documentation myself if preferred!

I would love to hear any feedback or thoughts from the core maintainers. Thank you for your incredible work on Gea!

Best regards,
KoHaRxnP

Start by reviewing the linked gea-query repository and npm package, then inspect this repository's documentation structure for an ecosystem or community-libraries section. Done means maintainers approve the listing and the official documentation includes the library with the relevant project links.

Written by the indexing model from the issue text.