Flexibility in the configuration

[valschmidt]

Our current implementation has a few hard coded paths and assumes a fixed directory structure. It also has topic names and fields hard coded. The result has been that with new releases of DriX or project11 software, the extraction of navigation fails. Or for missions that have multiple DriXs the archive folder format is different and so the model used here doesn't work well.

It would be useful to pull all of these things out of the code and into a config file. This would allow a user to customize where log files should be found, where the results of the data_manager should go, and what topics and fields the code should look for to accomplish various tasks.