Link from Users to Requests Doesn't Work When User Barcode Has Been Changed

This bug was reported by a colleague (Chalmers) and is currently affecting at least one real patron.

I reproduced it with test user 97362792-3403-41f6-801d-1792082575fa in Chalmers FOLIO environment.

Steps to reproduce:

1. Create a user with barcode "89101112"
2. Create an request on item A for this user
3. In the user record, verify that the user has 1 open request.
   
4. Click on 1 open request to look at this open request for item A in the Requests app.
   
5. Go back to the user record and change the user's barcode to "89101113". Save changes.
6. In the user record, verify that the user still has 1 open request.
   
7. Again, click on 1 open request to look at this open request in the Requests app.

Expected result:
Information about the user's open request for item A is displayed.

Actual result:
No open requests are found for the user.

However, I can find the request by replacing the user's current barcode in the search field with the barcode she had when making the request. Changing the user's barcode back to the one she had when she made the request also does the trick - but that's really not something you want to do when it comes to a real patron who lost their library card and got a new one...

Additional info from Cate:

• Let's solve this the same way we solved UIIN-821 (link filter should be by UUID, not barcode)

---------------------------------------------------------------
Additional info from Chalmers:

So, the problem seems to be something like this:

1. The request FOLIO uses to fetch a user's requests in the Requests app filters results by the patron barcode (why not the UUID?):
   https://chalmers.folio.ebsco.com/requests/?filters=requestStatus.Open%20-%20Awaiting%20pickup%2CrequestStatus.Open%20-%20Not%20yet%20filled%2CrequestStatus.Open%20-%20In%20transit&query=89101113
2. When I change the user barcode after making the request, there is a disconnect between the new user barcode used by the filter *and *the old user barcode still associated with the request. The new current user barcode thus returns no open requests.

Interestingly, requests-storage stores the user barcode from when the request was created. Compare the user object in these two requests made after I changed the barcode:

/request-storage/requests/154f2491-eafd-4178-80a7-077a1a8a9aa5

  "requester": {
    "firstName": "Christine",
    "lastName": "Daae",
    "middleName": "test",
    "barcode": "89101112"
  }

/circulation/requests/154f2491-eafd-4178-80a7-077a1a8a9aa5

  "requester": {
    "lastName": "Daae",
    "firstName": "Christine",
    "middleName": "test",
    "barcode": "89101113",
    "patronGroup": {
      "id": "bcbe3b01-ba07-4129-bfd8-ec528c1fb436",
      "group": "Public",
      "desc": "Public"
    }