DummyServer can fail to bind a port intermittently

[fracture91]

This happened during my team's automated testing:
http://tiki.cs.wpi.edu:8080/jenkins/job/dragonsparkles4/34/changes

It looks like the port to use is hardcoded. While unlikely, it's possible for that port to be in use. Ideally, we could bind to any high-numbered port that isn't in use.

java.lang.RuntimeException: java.net.BindException: Address already in use
    at edu.wpi.cs.wpisuitetng.network.dummyserver.DummyServer.start(DummyServer.java:60)
    at edu.wpi.cs.wpisuitetng.network.TestRequest.testRequestCommunication(TestRequest.java:209)
Caused by: java.net.BindException: Address already in use
    at sun.nio.ch.Net.bind(Native Method)
    at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:137)
    at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
    at org.simpleframework.transport.connect.SocketAcceptor.bind(SocketAcceptor.java:183)
    at org.simpleframework.transport.connect.SocketAcceptor.<init>(SocketAcceptor.java:100)
    at org.simpleframework.transport.connect.SocketListener.<init>(SocketListener.java:81)
    at org.simpleframework.transport.connect.SocketListenerManager.listen(SocketListenerManager.java:98)
    at org.simpleframework.transport.connect.SocketListenerManager.listen(SocketListenerManager.java:81)
    at org.simpleframework.transport.connect.SocketConnection.connect(SocketConnection.java:106)
    at edu.wpi.cs.wpisuitetng.network.dummyserver.DummyServer.start(DummyServer.java:58)

[jmpage]

Port is over 30000 on the master branch right now. The test should be modified to bind to an inactive port instead though.