Fix for extra 5 s stage scan time due to reading stale stage scan state value

[bls337]

@oleksiievetsno noticed an extra delay in stage scan. #404 was closed, but the delay turned out to be real, this is the fix.

The 1.4 plugin forces a fresh read of the stage-scan state (via RefreshPropertyValues); the LSM port was reading the cached value, which never updates to IDLE, so the cleanup wait always ran the full 5 s timeout and fell through to a forced Force-set XY stage scan to IDLE.

CoreLog validation: the 5 s tax is gone (stage-scan runs dropped from ~8500 ms to ~4600 ms, and the Force-set… fallback no longer fires):

STOP 1  3556 ms   Galvo scan
STOP 2  5128 ms   Stage scan
STOP 3  4570 ms   Stage scan
STOP 4  2297 ms   No scan
STOP 5  4564 ms   Stage scan
The residual ~1 s over galvo is the real physical stage retrace.

---