In error messages, displaying payments as { getAllegedBrand: [Function: getAllegedBrand] } is not very helpful

[DavidBruant]

Derived from a comment in support chat
But also based on my experience

The message that the person received was:

extent has duplicates: { getAllegedBrand: [Function: getAllegedBrand] } and { getAllegedBrand: [Function: getAllegedBrand] }

but as is, the message is unhelpful because it does not contain a description of the extent or the issuer.

I think that having more context in the error message would help making the error more helpful

[katelynsills]

I think we can close this, because it is actually printing the extent. The problem is that in this case, the extent is a payment, so there is no information printed besides the getAllegedBrand method. We wouldn't be able to improve the display-ability of payments in this scenario because we don't want them to be there in the first place.

[erights]

See #804 for our plan that enables presences to carry descriptions