Implement forceful killing of ongoing invocations

[tillrohrmann]

The forceful killing of an ongoing invocation is the hardest form of terminating an invocation. A forcefully killed invocation won't be able to run any compensations or other logic. The runtime will simply complete an ongoing invocation with an exception result that is propagated to its caller. Therefore, a forceful killing can leave the system in an inconsistent state and should always be the last resort.

Tasks

Preview Give feedback

1. Add invocation REST endpoint to metas #404
   +0
   
2. Add opaque service token to identify service invocation (service name, key, invocation id) #405
   +0
   
3. Introduce kill state machine command (partition processor) #406
   +0
   
4. Allow partition processor to abort executing invocations by invoker #407
   +0
   
5. Wire up node services with partition processors to be able to propose state machine commands #408
   +0
   
6. How to communicate the cancellation exception back to the caller? #409
   +0
7. Add e2e test for invocation killing #416
   +0