chore(dependabot): add 4-day cooldown, exempt Docker from cooldown -- Review and Merge

[timjensen-wk]

Summary

Part of the org-wide rollout of a 4-day Dependabot cooldown (to match JFrog Curation's 3-day window), with Docker/OS-image ecosystems exempted from cooldown entirely.

This repo had no .github/dependabot.yml before this PR — this is a bootstrap of a new, minimal config (per the batch's bootstrap override), not just a cooldown adjustment.

Ecosystems detected vs. configured (new file)

• pip (requirements.txt, requirements_dev.txt, setup.py at repo root) — new entry, cooldown.default-days: 4.
• docker (tests/functional/Dockerfile) — new entry, cooldown.exclude: ["*"] (OS-image ecosystem, exempt).
• docker-compose (tests/functional/docker-compose.yaml) — new entry, cooldown.exclude: ["*"] (OS-image ecosystem, exempt).
• No .github/workflows directory exists in this repo, so no github-actions entry was added.

New file

version: 2
updates:
  - package-ecosystem: "pip"
    directory: "/"
    schedule:
      interval: "weekly"
    cooldown:
      default-days: 4
  - package-ecosystem: "docker"
    directory: "/tests/functional"
    schedule:
      interval: "weekly"
    cooldown:
      exclude:
        - "*"
  - package-ecosystem: "docker-compose"
    directory: "/tests/functional"
    schedule:
      interval: "weekly"
    cooldown:
      exclude:
        - "*"

Notes

• Schedule interval defaulted to weekly (no pre-existing config to match).
• No registries: block; none added.
• Validated against the SchemaStore dependabot-2.0.json schema — no violations.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.