omm_detect_participant / omm_announce: RFID changes to alternative ID should not count as changes

[smathot]

Participants have two or more IDs. Right now, a switch between IDs belonging to the same participant result in omm.current_participant_changed returning True. To fix this, omm_announce should get all alternative IDs when announcing a detected participant, and these should be used in the _rfid_monitor of omm_detect_participant.

This may require an additional endpoint on the server.

[gdesor]

In the pull request, in order to remain consistent with theomm.current_participant_changedmethod, I reinstated the functionality that prevents adding an RFID chip number to the queue if it is identical to the previous one (the last_rfids variable in _rfid_monitor). Personally, I had removed it because it was causing me some issues.

For future revisions, I would suggest not including this type of filtering logic in _rfid_monitor. Instead, _rfid_monitor should insert every detected RFID into the queue, and this filtering should be moved to the omm.current_participant_changed method. That method would then compare the RFID used in the current experiment against all (or at least the last) RFID(s) stored in the queue.