Evict workflow from cache on RespondTaskCompleted failure

[Quinn-With-Two-Ns]

Evict workflow from cache on RespondTaskCompleted failure

closes #1357

[Sushisource]

Wow, crazy that was broken this whole time. Did this work with something like sending a complete where an activity is missing any specified timeouts? That's a common case where completing the task "fails" but I can't remember if that counts as the call failing or succeeds but with an error inside. Might be worth adding an integ test for that too since it's easy.

[Quinn-With-Two-Ns]

Did this work with something like sending a complete where an activity is missing any specified timeouts?

That wouldn't cause any issue before because when receiving the new workflow task the SDK would detect the cache as stale and evict at that point. This only causes issues in very specific scenarios that manage to bypass the SDKs cache checks and those situations are very hard to trigger with an integration test.