remote/coordinator: publish correct place after reservation re-scheduling

Fix a bug in schedule_reservations() where the update notification could
publish a stale/incorrect place due to reuse of a loop variable. Now it
publishes the place corresponding to the name whose reservation mapping
actually changed.

Signed-off-by: Alex Tercete <alex.tercete@arm.com>
Reviewed-by: Alex Tercete <alex.tercete@arm.com> # gatekeeper
Co-authored-by: Idan Saadon <idan.saadon@arm.com>

Author: alextercete

labgrid/remote/coordinator.py

@@ -1054,7 +1054,7 @@ def schedule_reservations(self):
                     place.reservation = res.token
         for name in old_map.keys() | new_map.keys():
             if old_map.get(name) != new_map.get(name):
-                self._publish_place(place)
+                self._publish_place(self.places[name])
 
     @locked
     async def CreateReservation(self, request: labgrid_coordinator_pb2.CreateReservationRequest, context):