(fix) Return IndyVdr based CredentialDefinition schemaId as full schemaId (not sequence number)

[gmulhearn]

indy ledgers will return creddef.schemaId as seqNo sometimes (see related openwallet-foundation/acapy#220 older acapy discussion), this is not a valid anoncreds schemaId, and is not consumer friendly.

This fix adds an extra ledger call (if necessary) to convert from schema seqNo to schemaId by resolving the raw txn and extracting the data. This matches acapy & credo's strategy:

credo-ts:

• https://github.com/openwallet-foundation/credo-ts/blob/main/packages/indy-vdr/src/anoncreds/IndyVdrAnonCredsRegistry.ts#L274
• https://github.com/openwallet-foundation/credo-ts/blob/main/packages/indy-vdr/src/anoncreds/IndyVdrAnonCredsRegistry.ts#L981

acapy:

• i believe acapy does still have the behaviour i'm trying to resolve here, but acapy does support resolving schema by it's seqNo: https://github.com/openwallet-foundation/acapy/blob/main/acapy_agent/ledger/indy_vdr.py#L496

[JamesKEbert]

Would a GH issue be appropriate on the ACA-Py side about this (given that we're adjusting it and Credo already has this behavior)?

[gmulhearn]

@JamesKEbert thnx for review. And yea acapy issue probably a good idea to re-discuss with them. Although I should probably re-test that it still occurs, my testing environment where it was happening a few months ago might be dated