feat: isolate inner schema to avoid name collisions

[andreitava-uip]

Context:

• Agent Builder agents have no restrictions to input / output argument names (other than the recently added reserved "messages"
• Due to how LangGraph state works, input and output args could conflict with internal state fields (ie: job attachments)"
• After lengthy debates, this has been the best solution left.
• Integrating the Guardrails state will come later.

[cotovanu-cristian]

this type of loop cross cutting functionality we should maybe extract in a /common package at the same level as /react as to be reused and not duplicated

[andreitava-uip]

true but for now i'd rather not prematurely extract packages when the hierarchy itself is not clearly defined. It should be easily done at a later date. If the plan is for us to reuse it within different loops of ours, we should think about where it should stay. If we want it to be usable by users directly (although in my opinion it is currently implemented with our state management in mind), it's a different story.