Galil: Investigate and fix position define on applying migration settings

[John-Holt-Tessella]

As a supporter, when I apply the motor settings from a batch script I do not wish it to redefine the motor position in the controller. Seen on SURF, to reproduce:

1. Start IBEX
2. Run script defining motor settings including motor and encoder resolution changes
3. Positions do not change, including motor readbacks, controllers now have different 0 defined, even after galil restart/ and or changing to SECI.

Acceptance Criteria

1. Procedure or fix is provided so that the migration can be performed without losing motor positions.

Notes

1. I suspect but haven't confirmed that when you change the motor resolution on a galil that the current position is kept and the new motor step value for that position is calculated and sent to the controller. This may be avoided by simply running the script before setting the IP address of the controllers. There may be other ways around this.
2. In the case where an axis can be homed, this is not a problem because the next task after running the migration script is to home all motors; thus setting 0.

[ThomasLohnert]

Not needed for reflectometry anymore as all axes have been migrated. Is this useful for other future migrations? If not, this can be closed.