Unique naming of JetCalibTool instances

This MR fixes the differences observed for jets when producing derivations with either Derivation_tf (CA) or Reco_tf.

The differences appeared because Reco_tf scheduled two instances of JetCalibTools with the same name but different configuration files (one for the actual calibration and the other for the calibration needed for fJVT). Thus the second instance of the calibration tool was also picked up for calibration of jets and the consolidated recommendations were used rather than the T0 calibration as done when running with CA. Now the tool names should be uniquely defined and in local tests, perfect agreement was observed for the jet four-vector.

This has only an impact on derivations, not core reco as we are not scheduling fJVT in core reco. Thus this should not violate frozen Tier-0 policy.

Tagging @jcatmore @tadej @schaarsc @sawyer @camacho @mswiatlo