CI(build-and-test): move part of the pipeline to a reusable workflow

[bayandin]

Problem

• build-and-test workflow is pretty big
• jobs that depend on the matrix job don't start before all variations are done. I.e. regress-tests depend on build-neon, but we can't start regress-tests on the release configuration until build-neon is done on release and debug configurations. This will be more visible once we add ARM to the matrix.

Summary of changes

• Move jobs related to building (build-neon) and testing (regress-tests) to a separate job

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]

3042 tests run: 2927 passed, 0 failed, 115 skipped (full report)

---

Flaky tests (1)

Postgres 14

• test_subscriber_restart: release

Code coverage* (full report)

• functions: 32.6% (6931 of 21275 functions)
• lines: 50.0% (54494 of 108968 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
e6bf243 at 2024-07-05T16:05:53.996Z :recycle:}