Wide Holds API Incorrect Queue Position on Patron-Focused Searches

Evergreen 3.8 -- Seen while working on bug #1904036

The new-ish wide holds API returns different values for relative_queue_position depending on how the API is called.

Specifically, when querying holds for a specific user, the API returns queue position 1 for all holds, except those where the patron in question has multiple holds on the same title. In other words, it only treats that patron's holds as potentially in the same queue as opposed to all holds.

To test:

1. Place multiple holds on a single title across different patrons.
2. Query the wide holds API via srfsh -- it's not yet exposed in the UI in EG master.

request open-ils.circ open-ils.circ.hold.wide_hash.stream "AUTHTOKEN" {"fulfillment_time":null,"usr_id":USER_ID,"cancel_time":null}, [{"request_time":{"dir":"asc","nulls":"last"}}], 100, 0, {}

Replace AUTHTOKEN. Replace USER_ID with the ID of each patron that has a hold on the test record. Each call of the API returns "relative_queue_position":1.