Investigate why `actions/setup-python@v5` fails sometimes in `I2::CI::check_for_incorrect_images`

[nxsaken]

The I2::CI::check_for_incorrect_images job fails sometimes with the following:

Error: The version '3.11' with architecture 'x64' was not found for this operating system.

Example log

[RamilMus]

Checked and found some closed and open issues regarding setting up python via this action. The recent one is open. And we have same log even though we use github runners with ubuntu-latest Unable to locate executable file: lsb_release

1. Do we need that workflow at all, is it useful for us? As I see it is intended to check that for main branch in all docker-compose files we will use iroha2-dev images, and for stable branch - iroha2:stable images, which is not actually true, we have different images in both branches. Guess it is not being useful anymore. Examples: for main, for stable

2. If we will need it, we need to reconsider allowed images in those docker-compose files and then for action itself we can try adding some workarounds like setting this lsb_release or rerunning this action inside the job.

[nxsaken]

@RamilMus nowadays we do releases via tags, and each gets a separate image (e.g. image for pre-rc.22.0). If we're keeping this job, it needs to be modified.