[demos] add Geniteam.move module with desired monster, farm, cosmetic…

[sblackshear]

… logic

This is my best attempt to understand what Geniteam wants as their smart contract logic. The idea is that they can use the

• create_ entrypoints to create players, monsters, and farms with some default attributes
• add_ entrypoints to equip farms with monsters and cosmetics, etc.
• update_ entrypoints to change the metadata associated with each of these
• remove_ entrypoint to de-equip a monster from a farm. If you want to equip cosmetics to a monster or update its attributes, it cannot be associate with a farm (at least for now)--you must remove it first.

For now, we add the module in the Sui framework because there is not (I think) an easy way to configure genesis to include modules other than the framework ones. Obviously, this module should be moved outside the framework once we can figure that one out.

[stella3d]

The code all looks good - the structs align with the Java classes, and I trust that you know the move-specific details.

Having a number of different methods for updates might make things harder for the demo team vs. having single bulky update methods for each type, but that's a limitation we're working around.

[sblackshear]

Having a number of different methods for updates might make things harder for the demo team vs. having single bulky update methods for each type, but that's a limitation we're working around.

Agreed. But I'm comfortable with pushing them toward using a smaller update methods, which I think will also push them toward putting more game logic on-chain (as we are hoping for).