Create "agent" socket type to handle full agent data from clients like discord, etc #55
Description
Right now we are using a purpose-built "Input Desctructure" component to get data from the agent and break it up without needing to define a lot of inputs per graph. This is not ideal. Since we end up using all of the agent data in lots of places, it makes out graph have a lot more sockets and nodes. We want to define a new agent type that passes all of this data in a single socket.
The agent destructure can still existing, and should have a corresponding restructure component even, but it should accept a specific socket type.
We might think about templating these nodes so a single structure / destructure can have a dropdown of template i/o or a custom option