[INJICERT-789]: Added a new wellknown endpoint for did.json and simplified the docker compose file

[vishwa-vyom]

New changes are tested in local docker compose setup.
Since rancher was not working, I was not able to test this in dev1 env.
But we can test in dev1 env using the below docker image once the rancher is up.

vishwavyom/inji-certify:release-0.10.x (Not additional config changes required, if the existing setup is in alignment with release-0.10.x branch, then these changes should work without any issues)

[vishwa-vyom]

http://localhost:8090/v1/certify/issuance/.well-known/did.json - this URL will provide the full did.json and the same can be hosted in a github page and the verification will start working without the need to use a python script to calculate the multibase.

Also later, helm chart can be changed to add a virtual service rewrite to use this as direct DID resolution URL.

[gsasikumar]

Hosting in GitHub pages is nothing to do with this correct? As per the issuer onboarding we should create the did.json automatically or we should let the issuer to configure his did.json from a different web or eth or another resolvers of his choice

[vishwa-vyom]

Hosting in GitHub pages is nothing to do with this correct? As per the issuer onboarding we should create the did.json automatically or we should let the issuer to configure his did.json from a different web or eth or another resolvers of his choice

That's right Sasi, this enhancement will provide a full did.json, which can we used for DID resolution.
Currently we use the GitHub pages for hosting the did json for did:web resolution, but we need to get the multibase of the public key using a python script to create the did.json file and then host in GitHub pages.