Test the output of the ETL

[aguynamedryan]

We should gather a handful of rows from each source file and hand-convert those rows into CDMv5, then feed those rows through our ETL and verify it generates the exact same rows. This will serve to test that our ETL process is properly functioning.

As we hit odd rows in the raw data, we can add them to our set of test rows and verify that we're covering all the weird edge-cases we discover during the implementation of the ETL.

[aguynamedryan]

We're working on hand-converting a few rows right now. If anyone else has already hand-converted some data, please let me know!

[ChristopheLambert]

We checked our output against the hand-coded source files and everything checks out. We have also tested the output of the ETL by loading it all into the CDM v5 and running Achilles Heel. After many iterations we removed all errors, with some remaining warnings that are well-understood and documented in the python_etl/README.md file.