Reorganize directory structure

[evanmayer]

Task

In order to make reading and maintaining code easier, the repo structure should have some logical organization that enables users to find specific modules and functions quickly. In order to avoid relearning, this should happen relatively soon, so users don't get too used to the current structure.

Avoid moving code between files (for now), try to keep reorganization at the directory level.

Acceptance

More folders than before, with better names

Details

Suggestions:

• Ground software
  • Separate by function or layer of TM/commanding stack
• Flight software
  • Separate configuration files, hardware interfaces, and algorithm code?
  • Separate motion control, detector readout, and telemetry?

[evanmayer]

Wontfix, because I won't be able to do the flight code side of the reorg on the given timescale, and I don't want to leave the reorg half-done.