Update the Bot UI

[guillefix]

Update the UI system: https://github.com/MetaGenAI/MetaGenNeos/blob/main/metagen/Bot/BotPanelUI.cs to grab references from a Neos-built UI, to make it easier to update the UI (and try sirkitree's UI prototype)

Similarly for the Animation UI, we can do the same https://github.com/MetaGenAI/MetaGenNeos/blob/main/metagen/Recorders/AnimationRecording/AnimationRecorder.cs#L291.

A workflow will need to be designed for this, where the Bot is able to grab a Slot reference when developing the UI. And then on production, the slot will upload that slot to its own Neos inventory, grab the Neos Cloud link, and use it in the future (by spawning)

[sirkitree]

Here's a general outline to approach this issue:

• Identify the UI elements and structure: Analyze the current UI implementation in both BotPanelUI.cs and AnimationRecorder.cs to understand which UI elements should be grabbed from a Neos-built UI.
• Create the Neos-built UI: Design and develop the UI prototype in NeosVR that will replace the current UI in the MetaGenNeos project. Ensure that the new UI includes all necessary elements and has a similar structure to the original UI. @sirkitree will provide this new UI in a new issue and link to it from here.
• Develop a reference-grabbing system: Create a system in the MetaGenNeos project that can grab references to the UI elements from the Neos-built UI. This system should be able to find and store the necessary Slot references for each UI element.
• Update the BotPanelUI.cs and AnimationRecorder.cs files: Modify both files to utilize the reference-grabbing system instead of the current UI implementation. Ensure that the new UI elements are properly integrated with the existing code and functionality.
• Design a workflow for development and production: Create a workflow that allows the Bot to grab a Slot reference while developing the UI. In production, the Bot should upload the Slot to its Neos inventory, retrieve the Neos Cloud link, and use it in the future by spawning the UI from the Cloud link.
• Test the updated UI system: Thoroughly test the new UI system to ensure it functions as expected and makes it easier to update the UI.
• Update documentation: Update any relevant documentation to reflect the changes made to the UI system and the new workflow.