Sync conf.yaml.example/config models with ddev + fix redis get_default_config collision

[philjlee]

What

Regenerates conf.yaml.example and config_models/{defaults,instance}.py for six integrations whose generated files had drifted out of sync with the ddev version CI now runs, and renames a colliding get_default_config method in redis_cloud/redis_enterprise.

Why

Drift fix: The Validate workflow's pip install ddev is unpinned, so CI validates against whatever the latest ddev release is (18.0.0 as of this PR), while these files were last regenerated with an older ddev. That mismatch has been failing ddev validate config/ddev validate models on master for a while — it's unrelated to any specific PR's content, but any PR that touches one of these directories (even just adding an unrelated file) drags the whole directory into TARGET=changed scope and inherits the failure.

Affected:

• conf.yaml.example: ocient, qdrant, redis_cloud, redis_enterprise, redpanda
• config_models: mergify, ocient, qdrant, redis_cloud, redis_enterprise

Method collision fix: OpenMetricsBaseCheckV2.get_config_with_defaults() in a newer datadog_checks_base calls self.get_default_config() to seed scraper config from generated model defaults. RedisCloudCheck/RedisEnterpriseCheck each pre-existing define their own unrelated get_default_config() (returns default metric groups), which shadows the base class's method and causes ValueError: dictionary update sequence element #0 has length N; 2 is required at check init. Renamed both to get_default_metrics to remove the collision — this is a pre-existing bug, unrelated to the drift fix above, but it also lives in redis_cloud/redis_enterprise and hits the same TARGET=changed scoping problem, so it's combined into this PR rather than split into a separate one (see note below).

How

• Regenerated with ddev validate config <check> -s / ddev validate models <check> -s using ddev 18.0.0 (matching CI), verified each is back in sync. No manual edits — every changed file is fully autogenerated from assets/configuration/spec.yaml.
• Renamed get_default_config → get_default_metrics in redis_cloud/datadog_checks/redis_cloud/check.py and redis_enterprise/datadog_checks/redis_enterprise/check.py, updating the one call site in each. Verified locally with ddev test redis_cloud/redis_enterprise (5/5, 7/7 passing) and ddev validate config/models for both, using ddev 18.0.0.

Note

This PR was originally split into two (this drift fix, plus a separate PR renaming the colliding method). Both touch the same redis_cloud/redis_enterprise directories, so under CI's TARGET=changed scoping neither could pass independently — whichever one didn't carry the other's fix would fail on the other's pre-existing bug when checked standalone. Combined them here; the separate rename PR (#3128) is closed as superseded.

This PR unblocks #3095 (TXP-277 dataflows.yaml backfill, batch 2), which is stacked on top of this branch.

🤖 Generated with Claude Code

[datadog-prod-us1-6]

🎯 Code Coverage (details)
• Patch Coverage: 78.38%
• Overall Coverage: 94.85% (+9.55%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 1a4a70e | Docs | View more details | Give us feedback!}