Marking results folders

During the release of version 6.3, I had some ideas for how to make the results easier to work with.

• Put the version of the pipeline in the doneprocessing file, so we can reliably identify which version the results came from, even if someone moves the folder.
• Maybe we should mark the version as failed instead of the entire run. That way you could try again with the next release of the pipeline. If a run breaks on the new version of the pipeline, you can still go back and look at the results from the old version. Maybe we need both, so you could tell the monitor to stop trying with a really bad run. This is a separate issue: #101.
• Make the Micall page display a warning with the results if it finds a results folder without the doneprocessing file. That way you can trigger a rerun by removing the doneprocessing or errorprocessing file without worrying about leaving an incomplete result set or having to clean out the entire result set. (That makes me nervous.)

Start by locating the code that creates or checks the doneprocessing and errorprocessing files, then trace the Micall page's handling of results folders. The issue's stated outcomes are to record the pipeline version, distinguish incomplete folders, and display a warning when doneprocessing is absent; version-failure handling is tracked separately in #101.