Handle edge cases within single decision batch

[wxing1292]

Currently, go client implementation does not handle the following case well:

1. child workflow creation & signal / cancellation within single decision batch
2. activity creation & cancellation within single decision batch
3. user timer creation & cancellation within single decision batch

Server side corresponding issue: cadence-workflow/cadence#2407