CI(build-build-tools-image): Do not cancel concurrent workflows

[bayandin]

Problem

build-build-tools-image workflow is designed to be run only in one example per the whole repository. Currently, the job gets cancelled if a newer one is scheduled, here's an example: https://github.com/neondatabase/neon/actions/runs/8419610607

Summary of changes

• Explicitly set cancel-in-progress: false for all jobs that aren't supposed to be cancelled

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

[github-actions]

2718 tests run: 2580 passed, 0 failed, 138 skipped (full report)

---

Code coverage* (full report)

• functions: 28.1% (6284 of 22345 functions)
• lines: 47.0% (44212 of 94108 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
a014afe at 2024-03-25T14:04:39.665Z :recycle:}