Enforcing ordering of Terminated wrt remote/local #2835

Due to the undefined ordering between Terminated messages it was possible for the RemoteDaemon to shut down and proceed with shutting down the Remoting before a Terminated was sent to remote watchers -- causing the message to be dropped.

I am not sure this is the best way to distinguish between local/remote ActorRefs, but the bug is confirmed to be fixed. Also, some feedback how this might affect cluster deployed actors is welcome.