fix: Properly unwrap optional data values

[dayaffe]

Describe the feature

In ShapeValueGenerator.kt we currently write ".data(using: .utf8)!, isClosed: true))" and ".data(using: .utf8)!". We should properly unwrap .data optional values rather than force them to be non-null using !.

Related comment:
// TODO: properly handle this optional with an unwrapped statement before it's passed as a value to a shape.

Use Case

Forced un-wrapping with ! should be avoided. Un-wrapping using other methods allows us to gracefully/explicitly handle unexpected null values.

Proposed Solution

No response

Other Information

Related issue: #710

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

[sichanyoo]

This ticket will involve changes that need to be made to all places where force-unwrap is currently done for assumed data type, as well as possibly creating a new error type that should be used for this case.

[jbelkins]

Closing since it is part of ongoing code review