Add defensive checking of sample names

[AmandaBirmingham]

Modify pipeline to ensure up-front that sample names meet naming convention (split into 5 pieces on a double underscore, start with "SEARCH-", maybe others) and to stop running and provide details of problems if any don't.

[kmfisch]

Also include automated check for merging or not merging based on the sample name, e.g. if two sample names are identical with the exception of the _L001 and _L002, then that would indicate it needs merging.

[AmandaBirmingham]

@kmfisch I'm going to break that out into a separate issue because (per this SP run evaluation thing) we still want to be able to run multi-lane data unmerged, so I see this as a new feature (instead of merged vs unmerged setting, we have merged, unmerged, and auto, where the code detects the merge setting based on sample name). See issue #122