Update .yaml workflows in update-python-config

[AAraKKe]

What does this PR do?

Extend the CI-files glob in `ddev meta scripts update-python-config` to also pick up `.yaml` workflow files (in addition to `.yml`).

Motivation

While reviewing Renovate PR #23481 we noticed several workflows still pinned older Python versions (e.g. `claim-pypi-name.yaml` was on 3.11, `dependency-wheel-promotion.yaml` on 3.13) even after past minor bumps. The reason: `update_ci_files` only globbed `*.yml`, so any workflow that uses the `.yaml` extension was silently skipped.

This PR makes the file selection cover both extensions and adds a regression test fixture (`claim-pypi-name.yaml`) to lock the behavior in.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the `qa/skip-qa` label if the PR doesn't need to be tested during QA.

[dd-octo-sts]

Validation Report

All 20 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov 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	✅
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

[datadog-prod-us1-3]

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 87.28%

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.78%. Comparing base (64e3557) to head (ab8d2e2).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.