Merge pull request #1085 from akka/wip-2974-escalate-uncaught-exceptions-√

Making sure that the current Threads' UEH is called when using Akka FJP ...
ignore automatically assembled files in akka-osgi resources dir
Merge pull request #1082 from akka/wip-2953-openBreaker-patriknw

Fix race in CircuitBreakerMTSpec.openBreaker, see #2953
Fixed mismatched RemoteConfigSpec with reference.conf
Merge pull request #1088 from drewhk/wip-fix-RemoteConfigSpec-discrepancy-drewhk

Fixed mismatched RemoteConfigSpec with reference.conf
Remove try ... catch constructs around invokations of tell, see #2870
fix the first of the issues: too strict test requirement, see #2950

LARS may execute recurring tasks a little too early on occasion, which
is a direct consequence of it trying to keep them running more regularly
and also allowing them to run at 1/tick rate.
make sure that InterruptExceptions are not swallowed, see #2963

also remove an old work-around in CallingThreadDispatcherModelSpec and
describe the rules for interrupting in the testing docs
Merge pull request #1068 from akka/wip-2950-LARS-∂π

fix the first of the issues: too strict test requirement, see #2950
move akka-io project into akka-actor’s akka.io package
clean up test output and help aggregation to pass on my Mac
deprecate old akka.actor.IO
correction of akka-osgi imports (missing imports)
first cut of the docs for typed channels
require “Actor with Channels” by using self-typing
change synthetic sender’s reply type to UnknownDoNotWriteMeDown
make all arrows invertible
Share same instance of deadLetters between LARP and RARP, see #2983
Generate ChildTerminated from all Terminated in RemoteDeploymentWatcher, see #2983

* The problem is that we do remote deployment to a node that isn't alive and with ordinary
  remoting that is not detected at all, as we know. With cluster this was taken care of by
  a later AddressTerminated and ChildTerminated generated by RemoteDeploymentWatcher. With
  the new RemoteDeadLetters the additional watch triggers an immediate Terminate which is
  captured by RemoteDeploymentWatcher but not acted upon since it's not an addressTerminated.
  RemoteDeploymentWatcher unwatch and will therefor not act on later AddressTerminated.
* The long term solution is to have reliable system messages and remote supervision without
  explicit watch, so that we know that the remote deployment fails.
* This short term solution is to let RemoteDeploymentWatcher always generate ChildTerminated,
  also for non-addressTerminated.
* It's possibly racy since ChildTerminated is not idempotent.
add docs on how to create child actors with channels