Support for hot code swapping about bastion HOT 3 CLOSED

For this feature will be necessary to implement a method for handling code updates. In Elixir / Erlang language exists the special method for handling. It described in docs, like here

from bastion.

We are still thinking for a feasible and reliable implementation for HCS. Though it is a very hard to implement feature we had a basic design document before. Sharing here so we can use it as reference:
https://paper.dropbox.com/doc/L50Ptr6lv8H7NjjomMeav

from bastion.

One of the ways to make it easier for implementation / usage / integration is to have a universal default registry (which is described in the issue #158) and available only for the main server (=handler/root supervisor?).
However, it also requires that any existing actor / supervisor must provide at least some minimal information for the default registry, such as used id /module_name. This kind of information will eliminate a lot of excessive work, so that the supervisor could update only the requested code with minimal memory footprint and shortest delays.

from bastion.