Improve Application Structure And Data Handling

[reid-spencer]

• groups/inputs/outputs remain the same but can have new alias names for syntactic sugar:
  • for groups : "page", "pane", "dialog", "popup", "frame", "column", "window", "section", "tab", "panel", "modal"
  • for outputs: "document", "list", "table"
  • for inputs: "form", "textblock", "button", "picklist"
• groups can already nest in groups but it should be possible to allow inputs to have inputs and groups of inputs, and outputs to have outputs and groups of outputs
• ability to send output of context calls to an input eg sending validation data to a modal written like step take input from Form to context EntityContext.Entity and outputs to Notification
• Allow inputs and outputs to handle any kind of data not just messages
• When input is sent to contexts or other backend definitions, they can only be commands and queries
• When output receives data from backend definitions, they can only be events or results