Support for More Pipelines

1. Reports in the same folder are merged and average, (We assume thart if there are different reports in the same folder, it only means that there are different brands in there.) Unfortunately, by doing so, the results may become inconsistent for reports that do not report coverage for certain
   files. Please make sure not to have different report brands (i.e. Clover and LCov together) for the same files. In that case, line coverage will be reported duplicate.
2. Exclude report option reportRejectList. Given the above, it may be difficult to manage that situation. We can then use this option to exclude a report that for some reason we don't want to consider for the overall coverage calculation). See example in .
3. Change file detection to include content. The check should be based on text labels and parsing should be avoided.
4. Remove files from the excluded list where applicable (code wise). Files in de excluded list are also used in a filename based algorithm. This needs to be changed. - I leave it there because coverage-final.json is not a part of any other report default naming strategy. This way I keep this protection.
5. Add support for Circle CI and BitBucket builds