Add DIDLint entry disable reports

[ankurdotb]

Summary

Reuse the existing DIDLint status output as the report-only signal for entry-level auto-disable. DIDLint no response results are treated as unresponsive failures; compliant, partially compliant, and non-compliant all count as responding so orange/yellow compliance issues do not disable drivers.

This PR is stacked on #548 and intentionally does not deploy or update UNIRESOLVER_DISABLED_ENTRIES. It writes report-only artifacts to the did-lint-reports branch: entry-disable-state.json, entry-disable-report.json, and disabled-entries.txt.

Behavior

• Maps DIDLint output back to application.yml driver entry ids using each entry's own testIdentifiers.
• Disables an entry in the report only after 3 consecutive runs where all of that entry's identifiers are unresponsive.
• Resets the counter and re-enables in the report when any identifier responds later.
• Keeps overlapping/multi-method entries enabled unless all identifiers owned by that entry are unresponsive.

Tests

• /tmp/ur-didlint-policy-venv/bin/python -m unittest discover -s ci/did-lint-check -p '*_test.py'
• bash -n ci/did-lint-check/run.sh
• git diff --check
• ruby -ryaml -e 'YAML.load_file(".github/workflows/nightly-did-lint-check.yml")'
• Smoke-tested policy against current did-lint-reports/result.json shape with temporary output files.