CI(promote-compatibility-data): take into account commit sha

[bayandin]

Problem

In #8161, we changed the path to Neon artefacts by adding commit sha to it but we missed adding these changes to promote-compatibility-data job that we use for backward/forward- compatibility testing.

An example of failed job: https://github.com/neondatabase/neon/actions/runs/9845717109/job/27186681258

Summary of changes

• Add commit sha to promote-compatibility-data

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]

3092 tests run: 2977 passed, 0 failed, 115 skipped (full report)

---

Flaky tests (3)

Postgres 14

• test_change_pageserver: debug
• test_statvfs_pressure_usage: debug
• test_pg_regress[4]: debug

Code coverage* (full report)

• functions: 32.6% (6939 of 21280 functions)
• lines: 50.0% (54556 of 109068 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
5d8c62f at 2024-07-09T08:48:00.967Z :recycle:}

[Bodobolero]

Thanks for fixing my oversight.