Enable issue cred v20 protocol for BC Reg issuer

[ianco]

Add support for v20 credential exchange. Specify the protocol to use using the env var ISSUE_CRED_VERSION - values are V10 and V20 (default is V10 if not specified).

This can be set for the container, or specifically for the cred submitter job as follows:

ISSUE_CRED_VERSION=V20 ./run-step.sh bcreg/submit-creds.py
ISSUE_CRED_VERSION=V20 ./run-step.sh bcreg/submit-creds_lear.py

[esune]

LGTM 👍🏻

@WadeBarnes I'll let you merge it when it is best to get the changes deployed and assessed in dev

[esune]

@ianco unsurprisingly this PR has become a bit stale and there are conglicts that need resolving now. Mind taking a quick look?

[WadeBarnes]

Are there any dependencies on the OrgBook side required for this to work? Also we have some comments here (bcgov/von-bc-registries-agent-configurations#79 (comment)) about the order we want to upgrade the ACA-Py versions. Are theses changes independent of those updates?

[esune]

Are there any dependencies on the OrgBook side required for this to work? Also we have some comments here (bcgov/von-bc-registries-agent-configurations#79 (comment)) about the order we want to upgrade the ACA-Py versions. Are theses changes independent of those updates?

I think if we use V10 things should work as they are now. If we switch to V20 we would have to update the OrgBook side as well since the webhook payload would be slightly different.

[esune]

LGTM 👍🏻

[WadeBarnes]

Changes have been deployed to dev and test.
cc @ianco @esune