Add jobs to test builds on different distros

[gurkanindibay]

With this PR, citus code will be tested in all packaging environments.
Sometimes, there can be compile errors which blocks packaging and in this case unplanned delays may occur.
By testing the code in packaging environments, I'm aiming to detect any compilation errors before packaging.

[onurctirtir]

Btw are those tests run in parallel to each other ? If not, that would affect development velocity very badly.

[gurkanindibay]

Btw are those tests run in parallel to each other ? If not, that would affect developer velocity very badly.

https://github.com/citusdata/citus/actions/runs/3489359842
it takes 4.5 minutes
it executes parallel

[onurctirtir]

1. This PR adds 22 more jobs; 5 x 3 for rpm based distros, which is nice, and only 6 for deb based distros. Are we sure that we're testing deb based ones for all supported pg versions ?

2. Also seeing lots of such warnings, can we fix them ? (as in https://github.com/citusdata/citus/actions/runs/3530829173)

3. For those gcc warnings, are we sure that we're using the correct gcc version (as you discussed with @JelteF in Teams chat) ?

---

(Btw this really looks good overall and I think we're very close to merge :) )

[gurkanindibay]

1. This PR adds 22 more jobs; 5 x 3 for rpm based distros, which is nice, and only 6 for deb based distros. Are we sure that we're testing deb based ones for all supported pg versions ?
2. Also seeing lots of such warnings, can we fix them ? (as in https://github.com/citusdata/citus/actions/runs/3530829173)

3. For those gcc warnings, are we sure that we're using the correct gcc version (as you discussed with @JelteF in Teams chat) ?

(Btw this really looks good overall and I think we're very close to merge :) )

1. Yes because the images are the actual packaging images. Whenever a new postgres version is released, I bake a new packaging image
2. These warnings about a Github Action checkout task. Updated the version and now it is OK
3. Yes. These are actual packages and the warnings are from the actual image that includes gcc that is the latest version that is being supported in the OS/release repo

[onurctirtir]

1. This PR adds 22 more jobs; 5 x 3 for rpm based distros, which is nice, and only 6 for deb based distros. Are we sure that we're testing deb based ones for all supported pg versions ?
2. Also seeing lots of such warnings, can we fix them ? (as in https://github.com/citusdata/citus/actions/runs/3530829173)

3. For those gcc warnings, are we sure that we're using the correct gcc version (as you discussed with @JelteF in Teams chat) ?

(Btw this really looks good overall and I think we're very close to merge :) )

1. Yes because the images are the actual packaging images. Whenever a new postgres version is released, I bake a new packaging image
2. These warnings about a Github Action checkout task. Updated the version and now it is OK
3. Yes. These are actual packages and the warnings are from the actual image that includes gcc that is the latest version that is being supported in the OS/release repo

1. I meant, I'm only seeing a single run for each one of those deb-all images, I believe we should have 3 jobs to test each one of them with 3 different posgtres versions ?

[gurkanindibay]

1. This PR adds 22 more jobs; 5 x 3 for rpm based distros, which is nice, and only 6 for deb based distros. Are we sure that we're testing deb based ones for all supported pg versions ?
2. Also seeing lots of such warnings, can we fix them ? (as in https://github.com/citusdata/citus/actions/runs/3530829173)

3. For those gcc warnings, are we sure that we're using the correct gcc version (as you discussed with @JelteF in Teams chat) ?

(Btw this really looks good overall and I think we're very close to merge :) )

1. Yes because the images are the actual packaging images. Whenever a new postgres version is released, I bake a new packaging image
2. These warnings about a Github Action checkout task. Updated the version and now it is OK
3. Yes. These are actual packages and the warnings are from the actual image that includes gcc that is the latest version that is being supported in the OS/release repo

1. I meant, I'm only seeing a single run for each one of those deb-all images, I believe we should have 3 jobs to test each one of them with 3 different posgtres versions ?

You're right. I changed to add all versions of Postgres for deb based distros now

[onurctirtir]

LGTM now, thank you for adding those jobs to Citus to early detect build time issues / before it's time to do a release 🚀.

Here is a checklist before merging, feel free to click check-mark symbols on each item as you move forward:

• Now it's time to get in touch with people in engine chat to ask for help to get those build warnings fixed (to be able to merge this PR)
• Please squash the commits before merging.
• After merging the PR into main, please backport this at least to release-11.0 / release-11.1 branches (and optionally to release 10.2 too) so that we can early detect build-time problems / before doing a patch release for those versions.
  Those versions of Citus are still actively supported and hence it's quite likely that we might want to release new packages for them at some point.

[hanefi]

Working functionality with several comments for increasing readability and maintainability.