Users need to modify the configuration/initial/akka.conf file to setup a cluster. To preserve the settings, we don't overwrite the file on feature re-install. This poses an issue for upgrades as important changes aren't picked up since the file already exists.

I propose we add a factory akka.conf that we always overwrite on re-install. In code we would overlay/merge the existing configuration/initial/akka.conf with the factory file. akka allows for a fallback config for this purpose. So it looks like we can load the configuration/initial/akka.conf with the factory config as the fallback and akka will take care of overlaying/merging. We can pare down the configuration/initial/akka.conf with only the pertinent settings that users need to set (i.e. host, port, seed-nodes and role name).

This will also help the integration tests which lays down its own akka.conf with the host, port, seed-nodes etc preset prior to startup. We recently saw test failures b/c the akka.conf template hadn't been updated with the Be changes. With this proposal the template can be pared down and the updated factory settings will be automatically picked up.