Remove XML configurations and runtime linking

[naegelejd]

Objective:

• Pingvin will no longer dynamically load libraries at runtime
• Pingvin will no longer load XML configurations

This is a high-level feature outline that must start with architectural design to determine how users will invoke Pingvin to run reconstruction workflows and individual Gadgets.

The outcome will include:

1. Removing runtime library loading
2. Removing XML configuration files
3. Consolidating all Gadgets that determine output data types into a single "Tail" Gadget that allows users to choose the output format with a parameter
4. Exposing all Gadget parameters as command-line arguments