PyRPOD configuration data requires streamlining.

[andytorrestb]

Currently pyrpod constructors are used to read in configuration data.

1. All config data should be consolidated so that it has to read in once not multiple times.
2. New method also needs to handle relevant edge cases when reading in configuration data. (ex empty file or incorrect format)

Linked below is the MissionPlanner constructor which demonstrates the basic functionality for reading in configuration data.
https://github.com/moon-mail/PyRPOD/blob/de786034df3fe60fbd76b9ff2209c4d99f71e6e7/pyrpod/MissionPlanner.py#L74-L92

This logic needs to be expanded/reworked to address the points discussed above.
Lastly, test cases should be updated to reflect this new work flow.

[andytorrestb]

Solution should include a debug/ testing statements as follows

`def print_config(self):`
    `for section in self.config.sections():`
        `print(f"[{section}]")`
        `for key, value in self.config.items(section):`
           ` print(f"{key} = {value}")`
       `print()`