Split /results and /data into a separate repository

[ahouseholder]

Having both the code and the data it is collecting in a single repository was neat when we started but the data has grown so much (and is updated so frequently) that it's impossible to follow the git commit history for the code anymore.

My proposal is to:

• retain the code & automation parts in this repository
• move /results and /data to a separate repository or repositories (there's no reason they can't be in the same repo, because the process that generates data into /results is distinct from the process that generates data into /data
• adjust the automation so that it updates the data in the new repositories instead of just reflecting it back to this one

Note that implementing thing would probably be a good time to consider implementing #1 as well.

[ahouseholder]

Fixing this might also address #7 and possibly provide an opportunity to address #10.