Create evaluation plug-in

[khatchad]

Fixes #31. Puts some parsing code in Core Utilities so that both UI and evaluation plug-ins can access it.

Commits

• I slowed down and took a deep breadth before committing. Otherwise, I will start a pristine branch and reissue this pull request.
• Before committing my changes, I checked my working directory carefully. I only staged the changes I wanted and ensured it was of the utmost quality.
• I used git diff and git status to check my work carefully before committing.
• I completely understand what I am committing and why.
• I completely understand why things are the way they are.
• The change I am proposing makes complete sense to me.
• For the most part, the changes in this pull request correspond to the problem or task I am solving or performing. In other words, only the changes that are supposed to be there are the ones included in this pull request.

Expectations

The plug-in can now be evaluated.

Testing

Six CSVs created with the correct headings and values.

Final Checks

• The changes I am proposing meet the expectations I have described above.
• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation if applicable.
• I have added tests that prove my fix is effective or that my feature works if applicable.
• New and existing unit tests pass locally with my changes.