Add UNTUNED_TOT_* variables to analysis output

Short description

Another victim of V1.1 chips not having ToT working correctly.

Input data

I think the input data is already being collected: running ToT scan before tuning is written in the procedures document, and is also part of run_full_qc.py script.

Analysis

Same analysis as for TUNED_TOT_*. But we are not going to cut on it.

Visualisation

Add same plots as for TUNED_TOT_*

Input to the production database

It's already in PDB since forever. (TUNING_UNTUNED_TOT_MEAN, TUNING_UNTUNED_TOT_SIGMA, TUNING_UNTUNED_TOT_95_LOW, TUNING_UNTUNED_TOT_95_HIGH)