Feature request: improve error message when Espresso Intent matching fails due to mismatched Intent data #2112

When Espresso Intent-matching fails to find a matching intent, it prints an error message:

that includes string representations of all expected Intents and all recorded Intents.

Currently, this error message obfuscates the data associated with each Intent, because ResolvedIntentImpl::toString:

relies on Intent::toString rather than Intent::toInsecureString.

This makes debugging difficult if the reason for the Intent matching failure is a discrepancy in Intent data. Ideally, ResolvedIntentImpl::toString would use Intent::toInsecureString rather than Intent::toString, but I don't know how feasible that is.