(crdt|eventsourced).Context vs. context.Context

[marcellanz]

We should have a story to enable user functions to get the context.Context from the gRPC server handler function in a clean way. context.Context shall be propagated (and not stored in struct types) by chained func calls, but having functions like

func handleCommand(c context.Context, ctx crdt.Context, ....)

is one context too much to bear for an API.

[marcellanz]

(crdt|eventsourced).Context will get the stream context embedded. Contrary to some wisdom in the packages documentation https://golang.org/pkg/context/
We do not embedd the context for other purposes than having it on the call stack and with limited lifespan of an entity running. There is a certain consent, that the recommendation by the context package should be relaxed golang/go#22602.