[Nolana BugFix] cross-tenant policy id causing 500 errors during circ. transactions

Overview:

The problem is sporadic.  After a FOLIO upgrade (new deployment), intermittent 500 errors occur in mod-circulation when check-out-by-barcode is called.

The logs show:

a call to : `RulesExecutionParameters(loanTypeId...

followed by

PolicyRepository Looking up policy <uuid that does not exist for this tenant>

SingleRecordFetcher  Fetching circulation policy with ID <uuid that does not exist for this tenant>

/loan-policy-storage/loan-policies/<uuid that does not exist for this tenant> null HTTP_1_1 404 9 0 tid=<tenant id> Not Found 

which causes the 500 error

The loan policy uuid exists for a different tenant on the same cluster.

mod-circulation was redeployed as an immediate work-around.

The error occurred for one of the tenants on the cluster (not all of them) after a morning Glory upgrade.  We saw a similar problem for one tenant in June during a lotus upgrade related to an overdue fine policy id (different cluster, different tenant).  There was a rally story to investigate further.  We thought it might have been caused by copy/paste of policies during the initial setup of rules for that particular customer but the seeing it again - seems like it's a bug.
Steps to Reproduce:

1. Multi-tenant environment
2. New deployment using snapshot of production database
3. Test checking out an item for each tenant.  Test several check-outs as the problem is intermittent.

Expected Results:

The correct loan policy id should be returned when the circulation rules are being evaluated.

Actual Results:

(See above)

Additional Information:
msuranofsky can provide logs.

version:  mod-circulation-23.1.5

Interested parties:

oleksandrkurash