Functionality for non-pairwise metrics

[LukeANewton]

as discussed with Cameron on Friday

some of the diversity metrics from the life sciences part of research are inherently non-pairwise. The metrics still move element-by-element through a collection, but compare every collection at once, instead of generating pairs of collections.

There is an easy way to do this that makes use of the infrastructure currently in place. Create an interface for these listwise metrics (eg. ListwiseStrategy). In the command pattern for the ComparisonService, add another command (ListwiseCommand) that takes a set of test cases and a ListwiseStrategy, and uses the ComparisonService code to execute the ListwiseCommand.

This will take some added code to the Controller and parser to let these commands be entered, but this first issue is just for adding the back-end code

changes to overall structure (new part in bottom-right)

order of onvoking services to achieve listwise command (same as pairwise, exception you dont need to generate pairs)