[Revert ]Merge Actor activation and first method/reminder call to user service.

[amanbha]

Currently 2 calls happen into user code when a method/reminder is invoked on an inactive actor:

1. Actor is activated.
2. Method/reminder is invoked.

Instead just invoke the ActorMethod and provide an optional header (or query param) to indicate activation before method invocation. SDK/User code can look at this header(query param) to determine whether it needs to be activated.

[yaron2]

I generally support that notion, however I don't like the use of headers unless absolutely critical.
Thoughts?

[amanbha]

A decision has to be made by SDK/UserCode, so a flag indicating ActivateBeforeInvocation needs to be passed from Actions runtime. It can either be a query parameter or a header.

[yaron2]

query param then.

[yaron2]

We need to open an issue for this in the spec repo to update the API endpoint, but only for the September iteration.
Can you do that?

[amanbha]

Corresponding spec issue: https://github.com/actionscore/spec/issues/10

[yaron2]

@amanbha I have some bandwidth to complete this for the current iteration, but that would involve a change in the SDK as well. Do you think you can make it or should we leave this item for the next iteration?

[amanbha]

@yaron2 Lets do it in next iteration.

[amanbha]

Actions runtime will not be able to distinguish between ActorActivation failure and method invocation failure. So it will try to activate the actor again even if the ActorActivation succeeded and only method invocation failed. Instead Actions runtime will revert the change to merge the calls made in this PR# #280