PriorityScoreFilter: throw error and stop or change design?

[julesjacobsen]

Currently supplying these:

  - hiPhivePrioritiser: {runParams: human}
  - priorityScoreFilter: {minPriorityScore: 0.501, priorityType: PHENIX_PRIORITY}

only results in a INFO (with a WARNING!):

INFO 11352 --- [           main] o.m.e.core.analysis.AnalysisStepChecker  : WARNING: Removing PriorityScoreFilter{priorityType=PHENIX_PRIORITY, minPriorityScore=0.501} as the corresponding Prioritiser is not present. AnalysisSteps have been changed.

This leads to incorrect results and likely confusion on the part of the user. Ideally the input parameters should not allow this to happen - i.e. the PriorityScoreFilter should only accept a minPriorityScore and it will filter the results accordingly. Like so:

  - hiPhivePrioritiser: {runParams: human}
  - priorityScoreFilter: {minPriorityScore: 0.501}

The requirement for the priorityType comes in part from the OmimPrioritiser not really behaving like other Prioritisers. It is really an inheritance mode score modifier.

This is related to #337 and #330