Local deployment of routers using config throws exception

[rogeralsing]

Found a bug in the local deployer when deploying local routers.
Changes in Akka.Configuration have improved our fallback support, which caused locally deployed routers to read a value from the fallback that was previously not found.
the "remote" setting for deployment returns empty string now, previously null.
We need to check for empty string also when determining if the deploy is local

[Aaronontheweb]

@rogeralsing this is part of the most recent changes, right - nothing that's made it into the NuGet package yet?

[rogeralsing]

I think it is from the multi level hocon fallback. and that is already in Nuget, right?

It has nothing to do with remoting or InjectTopLevelFallback or such.
There is a "remote" key for deployment, which contains the path to deploy to.
previously that key returned null, now it returns emptystring which is not tested for.

[Aaronontheweb]

actually nah, we're ok - most recent NuGet package is two weeks old. Your config changes came in less than a week ago.

We should definitely fix this before the next release.

[rogeralsing]

Closed by #363