Deploys a durable entity repository in context F, returning an instance of implementation-specific Deployment typed with the Repository algebra, wrapped in a resource (since deployments typically require finalization).

Repository operation uses the the interpreted repository, behavior and side-effect algebras, following a strictly defined sequence:

• the interpreted repository is used to create a handle on the entity with the specified ID implementing the entity algebra, so that the caller can interact with it
• when a function of the entity algebra is invoked, this invocation is serialized using the commandProtocol and sent over the wire thanks to CommandSender. On the receiving node, the message is decoded and run with the provided behavior interpreter: this typically involves reading the entity state (e.g. for validation), and writing events (which can lead to a new version of the state via the eventApplier function)
• after events were written, a possible side-effect is triggered: this can be asynchronous (i.e. the function doesn't wait for completion of the side-effect to return) but can be made synchronous by overriding the runModeFor method in the SideEffect
• the function finally returns to the caller with the result of the operation described by the entity algebra (reply value, typically encoded over the wire in a distributed deployment)

This interaction pattern occurs with "actor-like" semantics: all calls on the entity are processed in sequence.

The function is parameterized with the context F and the various involved types: S for entity state, ID for entity ID and Alg & RepositoryAlg for entity and repository algebras respectively (both higher-kinded type constructors).

Since the behavior described above involves concurrent handling of repository interactions and possible asynchronous side-effecting, we expect Async from F.

EntityIDCodec is used to encode/decode entity IDs to/from strings.