Storage failures due to `MorePassesRequired` are opaque and difficult to debug because its attributes are elided from logs

Storage operations might fail because the client no longer has enough ZKAPs to pay for the operation, because the client and server disagree on the number of ZKAPs required to pay for the operation, because the ZKAPs used by the client are not recognized by the server (bad signature, double spend, etc). There are likely other cases, too.

All of these cases are presented the same way in the server and client logs:

_zkapauthorizer.storage_common.MorePassesRequired: 

Since the point of the rest of the system is to maintain anonymity and de-correlate operations, there's little recourse to outside information when it comes to understanding the cause of these failures.

There is probably a lot of work to be done in this area but a start would be to just present the value of the attributes of this exception when it is logged.

Fortunately none of the values are particularly sensitive. They are either counts or indexes into a list of ZKAPs (the list itself is not an attribute).