feat: OpenID4VP Proof request Base work and UI

[MosCD3]

Summary of Changes

This PR introducing the flow of accepting a proof request from an issuer using OIDC flow

Related Issues

Please reference here any issue #'s that are relevant to this PR, or simply enter "N/A" if this PR does not relate to any existing issues.

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);
• Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
• 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 tests have passed.

PR template adapted from the Python attrs project.

[cvarjao]

I can understand that * is super generic, but any particular reason for setting to a very specific peer dependencies? Usually keep compatibility at major level (starting with ^) is fine. Similar comment for react-native-qrcode-svg, and react-native-reanimated changes below.

[MosCD3]

The "*" caused installing latest stable version, and it caused a whole lot of conflicts with other packages that are mot updated, and to do that in this PR is a big mess. I had to fix the version to get things aligned together and get the app to build and tests to succeed.

[MosCD3]

TBH, I believe leaving yarn to pickup latest updated versions for any packages is recipe for bugs. We have to dedicate PRs to solely update specific packages.

[cvarjao]

we can be specific at dependencies but more liberal with peer dependencies. Also, dependencies should not be updated as a side-effect, it should be explicit and managed by the lock file.

[cvarjao]

keep in mind that yarn install MAY produce unexpected dependency change. yarn install --immutable is the safest command to use and void unexpected changes to the lock file

[MosCD3]

I never meant to touch any of that :). It NEVER succeeded until I fixed versions for those packages. Let me know if you have another idea and we can hop on a call and discuss

[sonarcloud]

Quality Gate passed

Issues
11 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 SonarCloud