fix: AnonCreds proof requests with unqualified dids

[genaris]

Following issues found during integration with BCGov Wallet, where AnonCreds with unqualified identifiers are being used, here we try to adjust the identifiers used in a Present Proof flow depending on the proof request contents.

Basically, we analyze whether there is any restriction that contains an unqualified did and, if true, assume that we should use unqualified identifiers. Otherwise, we use the default ones (qualified).

I'm testing with BCGov wallet's main branch in both verifier and holder side and seems to work fine (at least with a basic presentation request using Person credential from BC Wallet Showcase.

[genaris]

cc @bryce-mcmath @wadeking98 hopefully this can solve the remaining issues with that awful thing popularly known as 'unqualified hell'.

[TimoGlastra]

Another great fix, thanks @genaris!

Do we need a simple test to cover this? (I'm fine with merging it as is to get it fixed ASAP)

[genaris]

Another great fix, thanks @genaris!

Do we need a simple test to cover this? (I'm fine with merging it as is to get it fixed ASAP)

I've added some based on v2-indy-proofs.e2e.test.ts (basically a copy-paste, maybe we can improve it in a future when reorganizing core modules). They fail when running with previous code and OK with these fixes, so it seems we are OK!

I'd like to wait for @bryce-mcmath feedback before merging, to make sure we are handling all relevant cases.