Rethink scenario definitions

[markpayneatwork]

Is your feature request related to a problem? Please describe. Scenario definition is currently pretty clunky. In particular, it requires knowledge of regular expressions, which is perhaps a higher level of understanding that we expect from most users, and a potential source of confusion. Can we find a better way to implement this?

Describe the solution you'd like Take advantage of the structured filenames used by most files. Tell KAPy what the field separator is, and then which fields it should use from the filename, and work the rest out from there.

Describe alternatives you've considered Many. But this seems to be the best solution

[markpayneatwork]

Experiment definition should now take place in association with the input configuration, in inputs.tsv