Checkqc

The ProcessPoolExecutor functionality has been removed from the web service, basically reducing it to running things in a blocking fashion. The problem with the ProcessPoolExecutor was that it spawned a lot of threads that were left running and wouldn't terminate properly. The most straightforward way to fix it is, for now, to remove the threading.

A Dockerfile has been added for running the web service in a container.

v.1.4.1
This is a bug fix release which makes sure that the undetermined percentage handler does not break when the yield is zero. Thanks to sarek928 for reporting it: https://github.com/Molmed/checkQC/issues/55

Minor update:
- Read length is now defined as the number of cycles run for a read. Read length intervals in config have been updated as an effect of this.
- Read length intervals are now lower and upper inclusive. This together with the new read length defintion solved issue 53 .
- Config usage have been moved from config to docs.
- The issue where a certain machine type, run type and read length combination can't be found in the config, will now be communicated to the user.

This release contains:
- Our paper submitted to [JOSS](http://joss.theoj.org/) on CheckQC
- Many improvements to the documentation, including building the docs using ReadTheDocs. The docs are now available at http://checkqc.readthedocs.io/en/latest/
- Simplified installation process, where Interop does not need to be installed manually prior to CheckQC
- The reads per sample handler did not report the threshold that was actually used as reported in https://github.com/Molmed/checkQC/issues/49. This has been fixed.
- The location of the bcl2fastq output directory is now configurable, with the default being the default used by bcl2fastq. https://github.com/Molmed/checkQC/issues/47

This minor release updates a few things:
- The log output will now include information on what type of runfolder was identified, which handlers are activated and how they are configured.
- It has been clarified in the README that we required python 3.5+. If there are a lot of people requesting support for older python version that is something that we might have to look into, but for now this is how things are.
- Better exception handling behind the scenes which should avoid some ugly stack traces, and make the error messages more user friendly (e.g. reminding the user that they have to run bcl2fastq before running checkQC if there is no `Stats.json` file).

These updates were based on the feedback from avilella, af8, senthil10 and ewels. Thanks!

- Fixes a bug in the way that the version flag was handled. It is now possible to use it without also specifying a runfolder.
- Improves the install process by excluding the tests, and including the default logging config in the distribution.

This release fixes two bugs:
- The monitored path for the webservice is now validated as the service is started
- A bug in the dynamic importing of the handlers meant the it was not possible to start CheckQC from any directory. This has now been fixed.