Separate squadron rendering from squadron component logic

[danbuis]

Goal of Pull Request

Separation of concerns leads to cleaner, easier to maintain code.

Testing "business logic" on a squadron shouldn't require spinning up an OpenGL env around it.

Potential Tasks

• [x] Meets the DefDone of the linked issue
• [x] All tests pass (Although the reviewer should run them to make sure)
• [x] New Renderer object in a new GUI package
• [x] Renders squads correctly

Any other pertinent information

A Squadron Renderer object has a squadron object attached to it. All user interactions will be with the Renderer, who will pass things to the appropriate function in the squadron object. Basically a small MVC sort of situation, where the renderer is both V and C.

[danbuis]

More files changed than I'd like, but that's because this touched our temp main class, several tests, and took a side trip through parsing to enhance some of the logging in there.