TAA Acceptance is being reset after agent settings update

[esune]

After updating configuration for an agent, it sometimes happen that the TAA Acceptance record is invalidated or lost, and the TAA needs to be accepted again. This seems to happen basically always when switching an agent from single-tenant configuration to multi-tenant configuration. However, it also appears that other changes (as experienced by @WadeBarnes this morning) might trigger this behaviour as well.

[WadeBarnes]

To confirm, we've seen this before when switching an agent from single ledger to multi-ledger mode. However this morning I was updating the configuration for some agents that were already in multi-ledger mode, and their TAA acceptance was reset.

The only configuration other than some additional ACAPY_AUTO settings was some prep for endorser protocol configuration. The update added the endorser configuration in a disabled state:

ACAPY_ENDORSER_ALIAS=
ACAPY_ENDORSER_ROLE=none
ACAPY_AUTO_REQUEST_ENDORSEMENT=false
ACAPY_AUTO_WRITE_TRANSACTIONS=false
ACAPY_CREATE_REVOCATION_TRANSACTIONS=false

[WadeBarnes]

I can't recall if we discovered a valid reason for the TAA acceptance being reset when switching from single ledger to multi-ledger mode (when rooted to the same ledger before and after), but it seems wrong that the TAA acceptance would be reset in either case.