Contributor vouch request: node-problem-detector compatibility scraper

[desheng01]

Hi Plural team - I would like to contribute a node-problem-detector
compatibility scraper under the repository's Contributor Program.

I checked the current scraper directory, manifest, open issues, and open pull
requests and found no existing scraper or competing submission for
node-problem-detector.

Proposed scope:

• add utils/compatibility/scrapers/node-problem-detector.py
• generate static/compatibilities/node-problem-detector.yaml
• register the add-on in static/compatibilities/manifest.yaml
• add focused offline tests for release filtering, version-to-Kubernetes
  mapping, Helm chart joins, fail-closed behavior, and scrape wiring
• preserve the upstream versioning rule documented by the project rather than
  inventing compatibility for the pre-v1.34 release scheme

Authoritative sources:

• https://github.com/kubernetes/node-problem-detector/blob/master/docs/versioning.md
• https://github.com/kubernetes/node-problem-detector/releases
• https://github.com/deliveryhero/helm-charts/blob/master/index.yaml
• https://github.com/deliveryhero/helm-charts/tree/master/stable/node-problem-detector

The upstream project changed to the v1.<k8s_minor>.<patch> scheme beginning
with the Kubernetes-aligned releases. The scraper would map v1.34.x,
v1.35.x, and future releases directly to the corresponding Kubernetes minor,
join the official Node Problem Detector Helm chart when a chart entry exists,
and omit older v0.8.x releases instead of guessing a compatibility range.

AI assistance disclosure: implementation and verification will be performed
with OpenAI Codex acting for this GitHub account.

Could a write collaborator please comment !vouch @desheng01 so I can open
the implementation PR and let the repository checks run?

[desheng01]

Implementation is ready and verified: #4368. It adds the Node Problem Detector compatibility scraper, generated compatibility data, manifest registration, and 7 passing offline tests. The PR was auto-closed by the vouch gate because this account is not yet listed. Could a write collaborator please !vouch @desheng01 so the PR can be reopened and checked?

[desheng01]

@michaeljguarino could you review the vouch request when you have a moment? The completed PR is #4368 and its only current failure is the expected unvouched-author gate. The implementation uses the documented NPD versioning scheme, includes generated compatibility data and 7 focused offline tests, and needs reopening once the account is vouched.