YAML support #72
Description
Rad currently has first-class JSON support, but we don't do much to explicitly support YAML, and so users have to rely on shell commands still to work with YAML.
parse_yaml
Equivalent to parse_json, but also handles YAML types (times, multiline strings, etc).
Unclear how exactly we should handle YAML times. Rad doesn't have a time type. Either we convert to something else, or we add time as a native Rad type (this would also have other benefits, but it's a complex type to execute well).
JSON Paths?
We should technically be able to apply our JSON paths logic to YAML files. But we need to double check, and also consider re-dubbing this to something like "data paths" instead, to be more universal, and then consider replacing json as a keyword, again with something more universal.
HTTP Integration
Currently, if we get a JSON response, we turn that into Rad native types. We should do similar with YAML responses (though are these really common?)
to_yaml
Convert Rad native types to a YAML string.
Ideally we make YAML feel as native as JSON does in Rad. YAML is a very common format, especially in the SRE/Kubernetes world, and we should cater to these use cases.