feat: bootstrap tm2demo

[moul]

Initial ideas for this PR:

1. Ensuring a robust and logical structure.
2. Crafting comprehensive and clear READMEs.
3. Implementing a fully functional client and server.
4. Including at least one integration test to verify system coherence.
5. Setting up a seamless GitHub workflow.
6. Revising the top-level and gno.land READMEs to provide clarity on the purpose of gno.land, highlighting both its intended functionalities and limitations.

Related with #1050
Related with #1102
Addresses #1189

[moul]

I need help obtaining reviews and assistance in either merging the current state if you believe it enables the next steps, or helping me complete it for merging.

cc @gnolang/core-contributors.

---

I have provided additional details here: link

Clarification on Project Philosophy:

It's important to rectify a common misunderstanding about the project's scope and philosophy. While gno.land, gnovm, and tm2 espouse a rigorous adherence to minimalism and simplicity, this doesn't imply that all extensions or tools related to the project should mirror this strict philosophy.

For instance, while the gnoland binary philosophy aims for minimalism, other components like gnosdk might accommodate more advanced tools and features. One example is the proposed introduction of proof of stake coordination tools or other advanced utilities. For those who envision gno.land being more akin to cosmos-sdk, the suggested approach would be to work directly within tm2 or gnovm (when the requirements align with the project's minimalistic principles). Alternatively, contributors can utilize the gnosdk top-level folder for functions that might not strictly adhere to the gnoland binary philosophy.

To further underscore this concept, consider reviewing and merging proposal #1105, which emphasizes the role of gnosdk as a suitable destination for ideas that aren't minimalistic enough for gnoland.

---

I aim to establish GnoSDK in this repository. However, at present, we don't need any specific features. Instead, we should concentrate on creating a well-organized project structure that facilitates easy contributions to gno.land and GnoSDK separately.

[moul]

We'll discuss during the upcoming team retreat.

https://github.com/orgs/gnolang/projects/15

[zivkovicmilos]

I agree with everything presented here, although I do think we need to discuss in detail how we see the GnoSDK as a project going forward, and pinpoint the exact functionality it will have

Thank you for the foundation 🙏

[moul]

Thanks @zivkovicmilos.

We're discussing this in #1201. We can modify this PR to align with the final decision.

[thehowl]

Putting in review meeting for next week so we discuss what to do with this

[thehowl]

From the GitHub review call:

• This should probably still be added, as @moul commented that this still marks a valuable place where to redirect people who want to bring contributions
• But a better place where to put this is more likely to be misc/tm2-demo or similar