[Feat] Behaviour for Registry

[sleipnir]

Describe the feature

Sometimes, due to the distributed nature of Spawn and the characteristics of our distributed registry (Horde), we may end up creating two instances of the same Actor. This will be properly detected by our net split logic and one of the actors will be terminated.

But even so, it would be interesting to provide alternative backends for our registry in order to allow the client to choose the behavior desired for the creation of our actors. This way, it would be possible to change the Registry implementation on the fly, allowing us to test different levels of consistency and even allow new features to be released because we can now support different topologies (a large one here, perhaps) of actors.

Why would that be important to you?

Ensure greater flexibility in actor generation

Additional context

We can try starting with the default registry being Horde.Registry and the available backends being:

1. https://github.com/eliasdarruda/ra-registry
2. https://github.com/alfetahe/process-hub.