Sorting

Trying to add following features to the sorting toolchain

1. Ability to set detection-method specific MoKSM sorting parameters. Currently this is implemented as a switch-case statement in the KalmanAutomatic makeTuples. It would make more sense to pull all parameter configurations into a table.
    * Started off by creating the table KalmanParams that serves as lookup table from detect.Methods -> set of parameters saved as a blob.
    * As @aecker pointed out, it might make more sense to treat this table as containing all parameters configurations used, and have KalmanAutomatic entries hold NPK field referring back to this table.
    * If we do this, we would still want a way to tell which set of parameter should be used automatically when populating KalmanAutomatic. Perhaps we should create something like KalmanDefault that serves as a lookup from the detection method to a specific parameter set entry in the KalmanParams?

2.  Ability to specify the name of the experimenter when performing KalmanManual step. I imagine this is a rather short-term feature. I would need others to elaborate more on the imagined use-cases.
    * To start it off, I've added Experimenter table, and modified KalmanManual to contain a PK referring back to an experimenter, allowing multiple versions of manually sorted set. Currently, it's made to choose only one person's version for further processing beyond the KalmanFinalize table.

I've made above-mentioned changes in the new schema called `mock` that points to a separate database from the `sort` schema. This is to avoid contamination of the `sort` database which is currently in active-use. Alternatively, I could have had the entire `sort` schema point to a different database on this branch, but I thought we'd like to use existing data to test out new features.