fix: blank v2 proof request notification

[bryce-mcmath]

Summary of Changes

Due to the change in functionality from V1 to V2, the body (usually the name field of the proof request) was missing for all v2 proofs. This change checks to see if a standard presentation object exists in v2 proofs and returns the name field if present. As with v1, it falls back to the comment, if no name is present. I added a comment highlighting the Credo API used and simplified the logic a bit, removing some unnecessary duplication.

Additionally I included some EOFs that myself and other developers were seeing as diffs every time we installed and built the project.

Screenshots, videos, or gifs

This is a screenshot of a proof request notification from VCAuthn, a service the BC Gov provides that uses the V2 protocol - as you can see the name is present

Breaking change guide

N/A

Related Issues

bcgov/bc-wallet-mobile#2125

Pull Request Checklist

Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

• All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this)
• If applicable, screenshots, gifs, or video are included for UI changes
• If applicable, breaking changes are described above along with how to address them
• Updated documentation as needed for changed code and new or modified features
• Added sufficient tests so that overall code coverage is not reduced

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!

Pro Tip 🤓

• Read our contribution guide at least once; it will save you a few review cycles!
• Your PR will likely not be reviewed until all the above boxes are checked and all automated checks have passed

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud