Making all online tests @Ignore to allow build to work with no Internet connection. Fixes #357

[TSavo]

Sometimes tests that require an active connection to exchange cause the build to fail because of a problem on the exchange side. This PR changes all the online tests to @ignore to avoid any possible build errors due to remote services being unavailable. Fixes #357

To find these I literally unplugged my internet connection and ran all the tests, only @ignore -ing the ones which failed.

[badgerwithagun]

I've been thinking about this one. Could we instead mark these with a @Category (along with. BitmexTest) or use an ...Integration suffix, and exclude them from the CI build using a Maven profile? That way the tests will still run when the build is run manually but we can avoid the CI build being flakey (or they can be excluded at the command line if you're working offline).

[badgerwithagun]

Or... Rather than using a profile, we could shift the matching tests to running in failsafe instead of surefire, and allow the build to pass if failsafe reports errors.

[TSavo]

Or... Rather than using a profile, we could shift the matching tests to running in failsafe instead of surefire, and allow the build to pass if failsafe reports errors.

I will look into that! :)

[TSavo]

Closing this PR to do a failsafe integration instead.