CI: use build-tools on Debian 12 whenever we use Neon artifact

[bayandin]

Problem

+ /tmp/neon/pg_install/v16/bin/psql '***' -c 'SELECT version()'
/tmp/neon/pg_install/v16/bin/psql: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/neon/pg_install/v16/bin/psql)
/tmp/neon/pg_install/v16/bin/psql: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/neon/pg_install/v16/bin/psql)
/tmp/neon/pg_install/v16/bin/psql: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /tmp/neon/pg_install/v16/lib/libpq.so.5)
/tmp/neon/pg_install/v16/bin/psql: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/neon/pg_install/v16/lib/libpq.so.5)
/tmp/neon/pg_install/v16/bin/psql: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/neon/pg_install/v16/lib/libpq.so.5)

From https://github.com/neondatabase/neon/actions/runs/11431912641/job/31801575309

Summary of changes

• Use build-tools:pinned-bookworm whenever we download Neon artefact

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.
• Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
• If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

• Do not forget to reformat commit message to not include the above checklist

[Bodobolero]

LGTM, let's try it with next test runs

[github-actions]

5229 tests run: 5015 passed, 0 failed, 214 skipped (full report)

---

Code coverage* (full report)

• functions: 31.2% (7564 of 24247 functions)
• lines: 48.8% (59902 of 122750 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
4d222b7 at 2024-10-21T10:39:55.688Z :recycle:}

[bayandin]

Tried on pg_regress workflows — it works