HOLD_RESERVATION_CONFLICT does not give meaningful feedback

[Rogan Hamby]

Sample scenario:

Item is checked in. The item may or may not have been checked out but it has an open reservation on the same barcode, which may or may not be the same item. There are other tickets discussing that rabbit hole. Regardless, the item is checked in to fill a hold targeting it but won't fill the hold because the reservation is open. I don't consider that a bug but looking at item status gives not meaningful information, nor does the user get feedback about the collision.

I'm seeing osrf logs with entries like:

circulator: item could fulfill either hold or reservation
circulator: pushing event HOLD_RESERVATION_CONFLICT
circulator: pushing event NO_CHANGE
circulator: BAILING OUT
circulator: bailing out with events: HOLD_RESERVATION_CONFLICT, NO_CHANGE

And the item simply checks in without a message.