Flow latency analysis runs with synchronous setting when the preference is asynchonous and vice versa

[reteprelief]

This problem did not exist in 2.3.3. It was introduced when we reworked how we pass on preference setting into the analysis.
see for example https://github.com/osate/examples/tree/master/latency-case-study