Update EDDP monitor into a BGS monitor

## Observed
(Broken out from issue #97)
EDDI relies on data from http://api.eddp.co, which is not up to date. Faction arrays with active and pending states aren't transmitted or handled appropriately by the server or the client.
- array data for faction active states, pending states, happiness, etc. are not handled by server,
- server returns localized names rather than ednames. Wherever possible, ednames should be made available.

## Investigation
Faction state changes are handled differently in that they are relayed more or less in real time from the EDDN TCP uplink. Though this is bounced through http://api.eddp.co, faction state changes should continue to remain relatively reliable. See https://github.com/EDSM-NET/EDDN/wiki for how this information is transmitted and EddpMonitor.cs for how EDDI receives the data.

http://api.eddp.co appears to be listening to 'FSDJump' and updating a database of faction states. When a faction state change is detected, the server fires off an update of its own for EDDI users to pick up. This update is currently a text string like
```
2018-02-10T22:11:55 EddpMonitor:monitor [D] Message is {"newstate":"None","oldstate":"Boom","systemname":"Alintun","x":-78.9375,"y":110.8125,"z":-36.0625}
```

Cross reference with https://github.com/EDCD/EDDP-API/issues/3.