chore(vc): update didkit package to openedx fork

[GlugovGrGlib]

Description

Replace the didkit Python package with openedx-didkit (v0.3.5) across all requirement files.

This PR only changes the requirements files, as openedx-didkit is a drop-in replacement for the didkit-python package and does not require any changes to application code. This also makes it safe to backport to Ulmo and Teak releases.

Supporting information

It was decided to fork the original https://github.com/spruceid/didkit-python package from SpruceID into the Open edX organization as https://github.com/openedx/didkit-python and publish it to PyPI as openedx-didkit and provide future maintenance (reference ticket).
The forked version updates the underlying DIDKit Core Rust library to add Verifiable Credentials v2 (VCv2) support and provides pre-built wheels for all Python versions >= 3.10, which resolves previous build and compatibility issues.

Testing instructions

This requirements update, along with other verifiable credentials fixes, was tested successfully in the e2e flow against:

• master
• release/ulmo.2
• release/teak.3

You can test it yourself by following the following steps:

• Build an updated credentials image to install the latest requirements
• Check that the built image includes the openedx-didkit==0.3.5 package and not didkit==0.3.3 pip freeze | grep didkit

Optionally test e2e VC issuing (installing from scratch or using https://lms.gliglu.rocks sandbox with creds: openedx/openedx):

• Follow https://docs.openedx.org/projects/edx-credentials/en/latest/verifiable_credentials/quickstart.html to setup verifiable credentials (use https://github.com/raccoongang/tutor-contrib-badges for tutor installation)
• Pass a course to receive a course certificate.
• Through the learner-record MFE create and issue a new VC to LC wallet application following instructions
• Check that Verifiable Credentials is valid, and passed all checks in the LC wallet.

[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.

[e0d]

Looks great. I did notice that the server you provide a link to isn't resolving.

[GlugovGrGlib]

Thanks, there was a typo now fixed.

[GlugovGrGlib]

Resolves #2956