feat: add runtime-safe resolver entry disabling

[ankurdotb]

Summary

Add runtime support for disabling resolver driver entries by stable entry id, without changing DID-method ownership semantics and without adding a new public probing API. Disabled entries are skipped during normal resolve/dereference and omitted from /methods and /testIdentifiers; overlapping enabled entries continue to work.

This PR keeps the deployment change limited to passing UNIRESOLVER_DISABLED_ENTRIES into uni-resolver-web via the generated app-config ConfigMap. The deploy path always writes the variable, including an empty value, so a later deployment can clear a stale disabled set. docker-compose.yml also exposes the same empty runtime environment variable for local visibility/parity.

No frontend changes are required. The deployed frontend reads /1.0/methods and /1.0/testIdentifiers from uni-resolver-web, so the UI follows the backend’s enabled entry surface. This PR intentionally does not include _entryId forced probing, probe tokens, report-only health checks, weekly status workflows, auto-disable state updates, auto-deploy, service type changes, resource limits, or pruning.

Documentation

• Documented required stable driver entry id values in docs/driver-development.md.
• Documented the disabled-entries deploy input and runtime behavior in ci/deploy-k8s-aws/README.md.
• Added UNIRESOLVER_DISABLED_ENTRIES to the uni-resolver-web Docker Compose environment as the local runtime knob.

Tests

• JAVA_HOME=/tmp/jdk17/Contents/Home /tmp/apache-maven-3.9.9/bin/mvn -pl uni-resolver-web -am test -Dcodegen.skip=true
• bash -n ci/deploy-k8s-aws/scripts/process-env.sh ci/deploy-k8s-aws/scripts/deploy-services.sh
• git diff --check
• ruby -ryaml -e 'cfg=YAML.load_file("docker-compose.yml"); env=cfg.fetch("services").fetch("uni-resolver-web").fetch("environment"); abort("missing UNIRESOLVER_DISABLED_ENTRIES") unless env.key?("UNIRESOLVER_DISABLED_ENTRIES")'
• catalog validation: 79 drivers, 0 missing ids, 0 duplicate ids