Update drivers with "latest" tag

The use of `latest` tags in universal-resolver has been one of the causes of excessive downtime in DIF's universal resolver (given its current setup). While universal resolver is not currently intended for production use, we recognize that it's a valuable tool for the decentralized identity community, and we're committed to ensuring it remains maximally available within our current means.

To improve Universal Resolver stability, we are doing the following:
1. Requiring that future driver contributions specify a version rather than using `latest`.
- Initially enforced via PR review
- Later we'll add an automatic check
2. Reaching out to last PR submitter of existing drivers that use `latest` to request that they update the driver to specify a version within 60 days

I've tagged the last PR submitter associated with affected drivers. I realize in many cases this person may no longer be responsible for the driver, so please help us track down owners.

We'll make every effort to track down owners and create individual issues if that helps. We _may_ need to temporarily disable drivers that can't be updated (if stability problems continue), but we will make every effort to work with the community to make all currently-maintained drivers available.

| Driver | Last PR submitter | Done |
| ---| --- | --- |
| aceblock/ace-did-driver:latest | @aceblockID | |
| bnewbold/uni-resolver-driver-did-plc:latest | @bnewbold | ✅ |
| caictdevelop/driver-did-bid:latest | @CAICT-DEV | |
| docknetwork/dock-did-driver:latest | @mike-parkhill | ✅ |
| dyne/w3c-did-driver:latest | @matteo-cristino | ✅ |
| evannetwork/evan-did-driver:latest | @S3bb1 | |
| ghcr.io/spruceid/didkit-http:latest | @clehner | |
| hacera/hacera-did-driver:latest | @hacera-jonathan | |
| halialabsdev/emtrust_did_driver:latest | @halialabsdev | |
| iotex/uni-resolver-driver-did-io:latest | @coderbradlee | |
| itpeoplecorp/tys-did-driver:latest | @bharadwajambati172 | |
| jolocomgmbh/jolocom-did-driver:latest | @chunningham | |
| k4security/kschain-resolver:latest | @sujiny-tech | ✅ |
| kataru/content-did-driver:latest | @MizukiSonoko | |
| mpgshankr/driver-did-mpg:latest | @mpgshankar | |
| ontio/ontid-driver:latest | @AlverLyu | |
| polygonid/driver-did-polygonid:latest | @ilya-korotya | |
| sphereon/uni-resolver-driver-did-factom:latest | @nklomp | |
| transmute/restricted-resolver:latest | @OR13 | |
| unisot/unisot-did-driver:latest | @mirkostanic | |
| veresone/uni-resolver-did-v1-driver:latest | @dmitrizagidulin | |
| viitorcloud/uni-resolver-driver-did-evrc:latest | @gourav-vc | |
| w744219971/driver-did-pdc:latest | @w744219971 | |
| zoeyian/driver-did-iid:latest | @InspurIndustrialInternet | |

Looking for owners:

- ghcr.io/kaytrust/driver-did-ev:latest
- gleif/did-keri-resolver-service:latest
- gleif/did-webs-resolver-service:latest
- radianceteamssi/everscale-did-resolver-driver:latest

Contained in this repo:

- universalresolver/driver-did-ccp:latest
- universalresolver/driver-did-indy:latest
- universalresolver/driver-did-key:latest
- universalresolver/driver-did-sov:latest
- universalresolver/driver-did-stack:latest
- universalresolver/driver-dns:latest
- universalresolver/uni-resolver-web:latest

Review the driver configuration for the listed universalresolver images and identify every reference using the `latest` tag. Check how existing driver versions are specified and replace only the affected tags with fixed versions, then verify the resolver configuration still references all intended drivers without `latest`.

Written by the indexing model from the issue text.