Medical Statemachine - Fix locality EH breaking current state

[PabstMirror]

Fix #7126
Problems from PR #6950

On locality change we have to do something to make sure state machine is in correct state
But I didn't realize how local EH actually works and each time a new client connected it was sending locality transfer events

This PR just uses the existing vars to determine state locally.

[commy2]

Can you explain how the Local event works with JIP etc?

[PabstMirror]

z1 (server):
localityChangedEH: _unit=z2, _isLocal=false

z2 (on init or jip):
localityChangedEH: _unit=z2, _isLocal=false
localityChangedEH: _unit=z1, _isLocal=false
localityChangedEH: _unit=t1, _isLocal=false
2 frames later: localityChangedEH: _unit=z2, _isLocal=true

So anytime somone jipped, it was sending a event with the Default state

[TheMagnetar]

I think this should be the case in order to send the latest information, specially if the medical states vary between clients (you have a completely different medical state and some information may be even lost). In any case, it should be done before doing a manual transition to a particular state in my opinion.