Support for routing a response to another pipe

When posting data to a service, it will sometimes return an array with e.g. an id, and a status on the individual record. This result can be merged back (correlated) into the source pipe in Sesam. That way it is possible to take further action on each record based on the result from the post operation. 

This is used when the target api doesn't have GET operations that can support the correlation behavior.

We currently implement this as a feature in microservices, where we push the result to a http pipe (using the sesam api and a token). This works, but it creates a weak link (not visual/tracked) between the system that receives the response and the pipe it is pushed to.