Input validation

[irgolic]

Implements input validation, as separate iterations in the logs. Still missing async tests, and some tests surrounding error raising are failing (pending discussion below).

A few last discussion points before this is ready:

• We don't raise exceptions on the 0.3.0 branch, what should be our strategy be for improper calling (e.g., prompt validation with msg_history passed)? Should we allow certain types of exceptions? What about for when input validation fails?
• In logs, should input validation be a separate Iteration, or should we add fields to merge it with the main one?

EDIT
I've introduced UserFacingException, any exc wrapped in it will be propagated to the user.
I've also added an exception field to Outputs, so we don't just store it stringified

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
guardrails	⬜️ Ignored (Inspect)	Visit Preview		Dec 7, 2023 6:11pm

[zsimjee]

It's looking good! Can you please add a notebook to exemplify input validation scenarios?

[zsimjee]

long control switch. Can we split some of the logic up?

For ex:
def start_message_history_action
def validate_msg_history_schema
def start_prompt_action
def validate_prompt_schema
def start_instruction_action
def validate_instruction_schema