Add discovery port name helper

[vitkyrka]

What does this PR do?

Add a discovery helper to get ports by name. This will be used in a new strategy which will allow ports to be selected using the name specified in the Kubernetes deployment. This strategy can be re-used by multiple integrations whose services use named ports for their metrics port, such as velero or argo_rollouts.

This helper is unused in this PR except for tests but is added in a separate PR following the example of earlier PRs where it was requested to keep changes to datadog_checks_base separate from other changes.

Motivation

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[vitkyrka]

• velero: add container-based config discovery support #24507 : 5 dependent PRs (#24459 , #24506 , #24512 and 2 others)
• Add discovery port name helper #24555 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[datadog-prod-us1-4]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 88.38% (+0.11%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 26b0664 | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run