Consolidate patron notes upgrade can break A/T events on standing penalties

[Galen Charlton]

The consolidate patron notes upgrade (see bug 1846354) renumbers actor.usr_standing_penalty rows if there are any actor.usr_message rows to fold in. However, we discovered an unanticipated consequence: there can be A/T events whose targets are ausp objects.

For example, in a stock system the following hooks target ausp:

penalty.PATRON_EXCEEDS_FINES
penalty.PATRON_EXCEEDS_OVERDUE_COUNT
penalty.PATRON_EXCEEDS_CHECKOUT_COUNT
penalty.PATRON_EXCEEDS_COLLECTIONS_WARNING

Any events that use those hooks will end up pointing to the wrong target after the upgrade. This would be a serious problem for any pending events that get processed after the upgrade, but would also be a problem for any completed events happen to be the subject of spelunking after the fact.

There are no stock hooks on aum or aun, so one solution would be to adjust the upgrade so that the original ausp ID values are guaranteed to be preserved (or at the very least, that any that are the targets of A/T events be preserved).

Noting this as a high-priority bug as it would block upgrades to 3.9 for anybody who has set up A/T events that target ausp.

Evergreen 3.9+