Test versions mismatch

[a-masterov]

Problem

We faced the problem of incompatibility of the different components of different versions.
This should be detected automatically to prevent production bugs.

Summary of changes

The test for this situation was implemented

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]

2810 tests run: 2715 passed, 0 failed, 95 skipped (full report)

---

Flaky tests (1)

Postgres 17

• test_node_status_after_restart: release-x86-64

Test coverage report is not available

_{The comment gets automatically updated with the latest test results
3d570a3 at 2024-09-30T16:24:28.866Z :recycle:}

[bayandin]

It would be nice to have a comment explaining what we are testing and why only these combinations.

Also let's use ids to make test names a bit more verbose (currently it's test_versions_mismatch[release-pg14-12]), I'm thinking about test_versions_mismatch[release-pg14-combination12], or maybe even test_versions_mismatch[release-pg14-combination01100]

[bayandin]

I'd try not to mix pathlib's API with os' counterparts, let's use pathlib.Path.mkdir instead, it should be something like:

target_dir.mkdir(parents=True)