TMSS-717: quick fix: for estimating the earliest_possible_start_time, we need the full duration of the scheduling unit, not just the longest one.

TMSS-717: added test to check if all scheduling_units created from any of the strategy templates can be scheduled with plain defaults. This should just work out of the box (and it currently doesn't as was discoverd during commissioning

TMSS-715: Update check for default piggyback values propagation, only for objects in the 'creating' state

TMSS-717: pick longest observations for timecontraints, not the target obs (cause not all scheduling units have a target obs

TMSS-666: TMSS-481 TODO: fix test, there are issues with permissions since we changed the method from GET to POST

TMSS-666: removed set_subtask_state_following_allowed_transitions from subtasks.py. It was moved in TMSS-725 to test_utils.py