Move Ground Station Closer to a Standalone Application

[pizzalemon]

There's some possible use in making Ground Station a standalone application, where it wouldn't necessarily be used for AUVSI SUAS. Instead, it could be used for general purpose flights, by UAV club in general perhaps.

Steps towards completing this:

• Have the user control the connection to Interop, and the connection to the UAV entirely through the frontend. (This may just be a goal aside from this subject because it seems to be a better system)
• Same type of control for the ODLC submission tab.

It is of note that this isn't especially important to the use of Ground Station, as its main purpose is for AUVSI SUAS. However, I would argue that these changes entail a better structure to the Ground Station.

[krishnans2006]

To extend this for current considerations, this is the ideal setup:

• ONE instance of the server
  • Running on ONE laptop/PC
  • Connected to the router
  • Exposed port for accessing the API
• MANY instances of the client
  • Running on various computers connected to the router
  • Each manages a certain task (these are what I can think of from the top of my head)
    • Quick data screen for managing flight and scoring (mission requirement)
    • Actions screen for modifying flight (important)
    • Logs screen for just quick logs access (helpful)
    • Submissions page for managing images and identifying coordinates, which can be used to modify flight path
  • All connect to the same groundstation server to access/modify the same data

THIS IS A COMPETITION REQUIREMENT! (or something similar)

We need a way to have multiple screens of the GroundStation displayed at the same time - that's the goal