If a completed present proof 2.0 webhook is not verified (failed state) see what we can log and/or bring to the UI

[loneil]

In the event a proof is shared but does not pass actually pass the verification (we have this happen with unknown revocation issues with the BC Wallet interoperability lawyer cases before) the webhook comes back but is not verified, triggering our failed status. See some details and screenshot: #703

In that code, if the webhook body DOES contain any relevant details about WHY it failed, we would like to return that to the UI as an expand error section. Kim has mockups.

Other/additonal options:

• Log out body or specific part on fail
• Adjust logging so we get an error level log?
• If webhook contains nothing useful, check if there's any ACA-Py enhancement that could be made to change that. Could check with community and raise an issue.