e2e: update to use compose v2, and don't depend on distro-packages

[thaJeztah]

• relates to Dockerfile: update ALPINE_VERSION to 3.18 #4354

We were depending on alpine's package repository to install compose, but for debian we used compose's GitHub releases. Depending on distro packages means that we don't know when updates will happen, and versions may diverge because of that; for example, alpine 3.18 updated to compose v2;

On alpine 3.17:

make -f docker.Makefile build-e2e-image
docker run --rm docker-cli-e2e docker-compose --version
docker-compose version 1.29.2, build unknown

On alpine 3.18:

make -f docker.Makefile build-e2e-image
docker run --rm docker-cli-e2e docker-compose --version
Docker Compose version v2.17.3

This caused our e2e script to fail, as it made assumptions about the name format created by compose, which changed from underscores to hyphens in v2;

Container cliendtoendsuite-engine-1 Running
Error: No such object: cliendtoendsuite_engine_1

This patch:

• updates the Dockerfile to install compose from the compose-bin image
• adjusts the e2e script for the new naming scheme format
• removes the version field from the compose-files used in e2e, as they are no longer used by compose.

- What I did

- How I did it

- How to verify it

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)