SC: Implement get_call_data, set_call_return_value and get_call_data host functions

[linh2931]

This PR implements the remaining sync call host functions. Basic sync call protocol level functionalities are in place.

Unit test basic_params_return_value_passing shows a complete end to end sync call in WASM code using the host functions in the following steps

1. making a sync call,
2. passing arguments,
3. saving return value,
4. retrieving return value

Resolves #1215

[spoonincode]

afaict we aren't enforcing max_sync_call_depth yet even in this PR. It feels like at least one of these PRs should have that enforcement? Since this one is at least enforcing max_sync_call_data_size now

[linh2931]

afaict we aren't enforcing max_sync_call_depth yet even in this PR. It feels like at least one of these PRs should have that enforcement? Since this one is at least enforcing max_sync_call_data_size now

I plan to enforce max_sync_call_depth after the refactor of apply_context is done (#1261, my next task), since that will change code structure. This PR focuses on the three host functions. I will create a task issue.

[spoonincode]

I might have missed it, but I think it would be worthwhile to have tests that have a 0 length call data, and 0 length call return data.

Also I see we're following the same pattern as action return data that makes it impossible to discern between an action that returned nothing and an action that returned a 0 length value. Consistency is good; just pointing it out.

[linh2931]

length

Good idea! I added #1297 for more tests in a future PR.

Right now I have get_call_data_less_memory_test for destination size 0 or less than required size.