Refined Proxy-based tests to work on travis + fixed non portable tests

Refined Proxy-based tests to work on travis + fixed non portable tests not going through proxies

The inJvm proxy is now explicitly started on loop back address 127.0.0.1. The SocketDestHelper now resolves any received hostname and compares it to 127.0.0.1. This should handle any loopback alias locally declared into /etc/host such as on travis-ci where localhost.localdomain was picked.

Fixed accessRandomApplicationUrl() and infoAvailableWithoutLoggingIn() to use the inJVm proxy as byteman was rejecting them as expected.