feat: parse string wrapped fixed values

[dpilch]

We should wait until after the demo to merge this incase there any last minute bug fixes.

Some props require json, number, or boolean values passed, but Smithy can only pass string.

The current schema says that we can receive boolean, string, and Date types directly, but I believe this is inaccurate. I have kept this functionality for now, but will check with the Studio UI team if this actually possible.

[alharris-at]

It may make sense to instead have a new data type with shape { jsonValue: } so we don't accidentally deserialize a json-ey string that the customer provides us. The only realistic situation I can think of where this would be an issue is if the customer wants to embed json as a string value, and we suddenly marshall it into an object.

[dpilch]

I had the same thought, but Studio UI team preferred to not change the SDK schema. I'll check with them again.

[dpilch]

I spoke with Harrison and Scott. They still want to use value and not jsonValue. They suggested that we look at the type of the component prop that the value is being applied to. If the the type is not a string then the value should be parsed.

[dpilch]

type field has been added to the fixed values schema. This will indicate if a value should be parsed or not.