bitspark API wrappers

[Desrever Nu]

They use patio in theory

[Desrever Nu]

https://bitspark.io/documents/api_v2

[Sam Griffiths]

BitSpark wrappers now exist in branch feature/BitSpark. They are a copy of the existing Peatio Wrappers used on the internal exchange with a few edits to point them to bitspark instead. i have tested the base functionality using TestWrappers.java and they work as expected. Deeper and independent testing will be required though.

[Desrever Nu]

Oh, I thought we could reuse the PeatioWrappers and just change the api entry point when constructing the object .

If you think that bitspark requires its own modification than you took the right approach, otherwise we would see several switches in peatioWrapper

[Sam Griffiths]

I thought that it would future proof the wrapper if bitspark ever make modification outside of peatio

[Sam Griffiths]

I have tested against bitSpark and am happy with the functionality of this wrapper. Merging into develop ready for full tests

[Desrever Nu]

need to test it the wrapper integration with nubot

[Desrever Nu]

Before closing this issue we should make sure it is integrated into nubot.

Currently, for example, the bot won't start for bitspark.

Need to edit the Exchange.java file adding it to supported exchange and also edit the README.md with the admitted valued updated.