opportunistic capture can fail to find relevant holds

The list of potential holds that an item might fill returned by open-ils.storage.action.hold_request.nearest_hold can contain duplicates entries. The duplicates occur for each non-blocking standing penalty after the first for the patron associated with a candidate hold - and the notes consolidation change likely means that there are more of them.

As a consequence, opportunistic hold capture can end up doing redundant hold permit tests, thereby wasting some of the up to 100 candidate holds returned by the nearest_hold method. Empirically, this has resulted in opportunistic hold capture failing to target holds that could have been filled (for a really popular title).

Evergreen 3.9