The v4_set_baseline route currently always sets the session baseline
using the default key (passing ts_name=None implicitly), however the
logic to actually look up the baseline (get_baseline_run in
testsuitedb.py) always uses the ts-specific key. This mismatch means
that generate_run_data fails to look up the correct baseline and instead
always uses the default fallback.
It appears that the implicit default parameter to baseline_key is never
relied upon in a way that isn't broken, so we simply remove the default
and pass ts.name explicitly everywhere.