[Feature Request] Confirm async activity completion can give null value for Optional-return activity

[cretz]

Is your feature request related to a problem? Please describe.

Reading the code, it looks like we just don't put a value instead of putting a single null when the result is given None. Make a test to confirm that is ok for a workflow expecting an activity response of Optional[str] or similar.