Can't build sal-remoterpc-connector w/o a network interface that is up and has an IP address.

I was trying to work on a plane and so I had all of my network interfaces down and I got build errors looking something like this:

10:51:40.638 [main] DEBUG o.o.c.s.c.remoterpc.ServerImpl - Remote RPC Server is starting...
10:51:40.639 [main] DEBUG o.o.c.s.c.remoterpc.ServerImpl - Trying address /fe80:0:0:0:0:0:0:1%1
10:51:40.639 [main] DEBUG o.o.c.s.c.remoterpc.ServerImpl - Trying address /0:0:0:0:0:0:0:1
10:51:40.639 [main] DEBUG o.o.c.s.c.remoterpc.ServerImpl - Trying address /127.0.0.1
10:51:40.639 [main] ERROR o.o.c.s.c.remoterpc.ServerImpl - Failed to find a suitable host address
10:51:40.639 [main] ERROR o.o.c.s.c.remoterpc.ServerImpl - Remote RPC Server could not acquire host ip address. Stopping...

...

Failed tests:
ServerImplTest.start_Call_ShouldCreateNZmqSockets:128 ZMQ Context does not exist in Remote RPC Server
ServerImplTest.start_Call_ShouldSetServerStatusToStarted:116 expected:<STARTED> but was:<STOPPED>
ServerImplTest.start_Call_ShouldCreate1ServerThread:136 expected:<1> but was:<0>
ServerImplTest.start_Call_ShouldCreateNHandlerThreads:150 Server is in illegal state. ServerHandler does not exist

After bringing up the wifi interface and attaching it to the in-flight AP, I was able to build without problems. We should really try to avoid dependencies like this if we possibly can.