Fix dependency on neon-image in promote-images-dev

[jcgruenhage]

Problem

871e8b3 failed CI on main because a job ran to soon. This was caused by ea84ec3. While promote-images-dev does not inherently need neon-image, a few jobs depending on promote-images-dev do need it, and previously had it when it was promote-images, which depended on test-images, which in turn depended on neon-image.

Summary of changes

To ensure jobs depending docker.io/neondatabase/neon images get them, promote-images-dev gets the dependency to neon-image back which it previously had transitively through test-images.

[github-actions]

7348 tests run: 6971 passed, 0 failed, 377 skipped (full report)

---

Flaky tests (5)

Postgres 17

• test_scrubber_physical_gc_ancestors[None]: debug-x86-64
• test_metrics_normal_work: release-x86-64, debug-x86-64
• test_timeline_ancestor_detach_idempotent_success[shards_initial_after2]: release-x86-64

Postgres 16

• test_location_conf_churn[3]: release-arm64

Code coverage* (full report)

• functions: 33.7% (8437 of 25068 functions)
• lines: 49.1% (70546 of 143613 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
71b8141 at 2025-01-17T14:28:31.236Z :recycle:}