Unify return values in DSL

[niknetniko]

Fixes #403.

This changes the DSL to have one attribute for return values: return. Then, to decide how to handle it:

1. If the value is an untagged YAML string; interpret it as the string (Python) representation.
2. If the value is an untagged object; interpret is as the advanced output channel object (for oracles).
3. Else, interpret it as a value, like the current return behaviour.

Additionally, it introduces an additional tag, !v to explicitly mark a value as a YAML value. Some examples:

• return: 5 is a value, an int
• return: [5, "old"] is a value, a list
• return: "{5, 5}" is a string representation, thus a set
• return: !v "{5, 5}" is a value, a string
• return: !int8 5 is a value, an int8

In most cases, this will make the test suites easier, as both statements, expressions, return values and oracle arguments all use the Python syntax by default.

This change is not backwards compatible. I'll need to go though the repositories to see where we must change usages:

• All return_raw must become return.
• All return with a string or object need the tag !v.

[pdawyndt]

Maybe we should use a more explicit name then !v to improve readability.

[niknetniko]

Maybe we should use a more explicit name then !v to improve readability.

I went for !v to reduce clutter; e.g. if you have a string return value everywhere, that's a lot of times "value" will be there.

However, better readability is also something we want, so perhaps it is better to be explicit.

[niknetniko]

We now support both !v and !value