Currently, there is no way to specify most parameters when requesting darks via MyMDC - values are
just loaded from the calibration configurations repository.  To allow for using different offset
thresholds in fixed gain mode versus adaptive gain mode, adding these extra parameters is a
pragmatic if not elegant solution for now.

The relevant data is copied into memory in pretty large chunks, so the core driver is not expected
to do much for us here.  In some brief testing, using the default driver instead resulted in
approximately the same (or slightly better) runtime and significantly lower peak memory consumption.

This requires the pending MR for cal_db_interactive.  Tested with e79f2c9d (current head of the
branch of that MR).

Applying isort and nbstripout.  Changing from ipyparallel to multiprocessing - and while doing so,
simplifying the call signature of characterize_module.

Add webservice.parse_config test

See merge request detectors/pycalibration!427

Add Merge Request template

See merge request detectors/pycalibration!356

See merge request detectors/pycalibration!424

Add runtime summary to calibration metadata

See merge request detectors/pycalibration!418

It was just a warning for summary.rst, but might as well.

Fix/DSSC DARK was missing from the new mapping modifications

See merge request detectors/pycalibration!425

Add test for webservice.merge

See merge request detectors/pycalibration!423

Remove duplicate operation_mode parameter in FastCCD notebook

See merge request detectors/pycalibration!422

[MAPPING][DARK][INJECT] PT2 Update injecting functions and Dark notebooks

See merge request detectors/pycalibration!416

Fix/3.0.0-test04 on max-exfl017: proposal-yaml, AGIPD correct, PnCCD notebooks, and DSSC dark

See merge request detectors/pycalibration!420

Make get_dir_creation_time use files creation dates, not folder

See merge request detectors/pycalibration!421