Do not automatically re-execute on step enter triggers after a user change happened or a Tulip session is reestablished

At present if a user switch happens mid-process or a previously closed Tulip session is reestablished (e.g. the operator accidentally close the player and reopens it again afterwards) all “on step enter” triggers are re-fired.

Depending on what is going on with these triggers this may lead to undesired behavior that is - depending on the situation - only difficult to resolve by other means.

At least there should be an option then to decide which ones should re-trigger and which shouldn’t.