fix(vc): update obv3 achievement id format to urn compatible

[GlugovGrGlib]

Description

This fix is a part of work to improve compatibility with the latest version of LC Wallet: #2956.

The PR updates the credential UUID format to URN-compatible when building the "Achievement" body of the Open Badge 3.0 credential.

Supporting information

LC Wallet displays "Invalid Signature" warning when issuing a new credential from the Open edX.
The issue is reproduced starting with version 2.1.0 of the LC Wallet. At the time, verification algorithm was updated and extracted into the separate library verifier-core.

Testing instructions

• Either use sandbox installation with verifiable credentials setup https://lms.gliglu.rocks or set up and configure verifiable credentials, including the issuance entity and issuer key.
• For a user with an issued course or program certificate, go to the Verifiable Credentials section in Learner Record MFE.
• On the selected certificate, click the Issue button and Scan QR code with the LC Wallet App.
• Check verification status in the LC Wallet app.

[openedx-webhooks]

Thanks for the pull request, @GlugovGrGlib!

This repository is currently maintained by @2U-aperture.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.