ci(dependabot): removed the paths filter from the auto-merge caller

[karlspace]

Why

The Dependabot auto-merge caller (.github/workflows/docker-maintenance.yml) only started for src/rabbitmq/Dockerfile and src/rabbitmq-init/Dockerfile. A pip update of rabbitmq-init (requirements*.txt, e.g. #6) never reached the module: no decision, no annotation, the PR just stayed open. The module should react to every Dependabot ecosystem configured here and leave a visible decision on each PR.

What

• Removed the paths: filter from the caller's pull_request trigger (types opened, synchronize, reopened, ready_for_review kept).
• Rewrote the header comment to describe the new trigger scope per ecosystem. The old comment also claimed the merge triggers docker-release.yml, which a GITHUB_TOKEN merge does not.

Nothing else changed: required-workflows: .github/workflows/docker-release.yml, merge-method: squash, auto-approve: true, secrets: inherit and the permissions all stay as they were. The repository is public, so the module does not need the checks/statuses/actions: read scopes. docker-release.yml needs no wider paths:: its pull_request trigger already covers src/**.

Ecosystem (dependabot.yml)	Prefix	Auto-merge now	Why
docker /src/rabbitmq, /src/rabbitmq-init	chore(docker)	yes (unchanged)	The docker-release.yml PR run builds both images (push: false) after compose and shell validation and the rabbitmq-init tests
pip /src/rabbitmq-init	chore(deps)	yes (new)	docker-release.yml runs on src/**. test-init installs requirements-test.txt (which includes -r requirements.txt) and runs pytest. docker-build-init-pr builds the image, whose Dockerfile COPYs requirements.txt and installs from it
docker-compose /	chore(deps)	n/a	Every image: is ${VAR:-...}:${VAR:-latest}, our own images and traefik-certs-dumper on floating latest. Dependabot cannot update these and has opened no compose PR since June
github-actions /	chore(ci)	no (manual)	The module's own guard leaves GitHub Actions updates and any other .github/ change open

Only patch updates are merged (the module default for merge-update-types). Minor and major updates, such as #6 (pytest 9.0.3 → 9.1.1, semver-minor), are left open with a notice. None of the prefixes cuts a release: chore produces no semantic-release bump, and the GITHUB_TOKEN merge starts no push run.

Compatibility

• Docker base-image PRs go through exactly the same path as before.
• Pull requests that Dependabot did not open now also start the caller. The module's job filter skips them (one skipped check), and nothing is merged.
• Open Dependabot PRs (chore(ci): bump actions/checkout from 6 to 7 #5, chore(deps): update pytest requirement from <10,>=9.0.3 to >=9.1.1,<10 in /src/rabbitmq-init #6, chore(ci): bump actions/setup-python from 6 to 7 #7) get a decision on their next event (rebase, push or reopen).

Test

• Parsed the YAML locally: the trigger is pull_request with the four types and no paths, and the permissions and with: inputs are unchanged.
• This PR changes only .github/, so docker-release.yml does not run on it. Its CI shows the caller starting without a paths filter, with the maintenance job skipped because the PR is not from Dependabot.
• After the merge, the real proof is the next Dependabot pip PR: the caller runs, waits for docker-release.yml, then merges a patch update or leaves a minor or major update open with a notice.