fix(deps): update driver, tests and examples for did:near

[GeinerGV]

Using driver version 2.0.0 which update resolver to did resolution result

Features:

• update did:near resolver to the most recent version that is did-core-spec compliant and also provides a valid JSON-LD @context
• update did:near resolver to support multiple networks (see did:near:alice.testnet and did:near:alice.near)

[BernhardFuchs]

Sorry for the delay in testing this. I just ran the CI pipeline and the driver does not get updated because it is using the latest tag. Therefore one of the example DIDs is not working.

We changed our recommendations to not use latest tags a while ago as can be seen in the docs and end of last year we also followed through with this on a technical level. Since then there is no guarantee that an image with latest tag will ever be updated.

The underlying reason for this change is that the previous approach was to recreate the whole namespace with all images on every deployment. This resulted in quite some downtime and with the project growing, also in instabilities and a broken service.

What you can do now:

• Create a versioned tag for our image
• Update the docker-compose.yml with the tag
• Let me know here that you have done this

[GeinerGV]

Thanks for the explanation.
I’ve created a versioned tag for the image and updated the docker-compose.yml accordingly. The CI pipeline should now pick up the correct version and the example DIDs should work as expected.
Please let me know if you’d like me to adjust anything further.