[CI] Docker commands failing in the integration test for running stack command in Windows

[mrodm]

Starting on Sept 16th, the step in CI in charge of testing elastic-package stack command on Windows failed due to errors related to docker like this one:

Error: failed getting stack status: error getting containers with label "com.docker.compose.project=elastic-package-stack" (stderr="error during connect: this error may indicate that the docker daemon is not running: Get \"http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.47/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.project%3Delastic-package-stack%22%3Atrue%7D%7D\": open //./pipe/docker_engine: The system cannot find the file specified.\n"): exit status 1

Docker info command also showed that there is some issue with the Server (daemon):

Client:
 Version:    27.2.1
 Context:    default
 Debug Mode: false
 Plugins:
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.3
    Path:     C:\ProgramData\Docker\cli-plugins\docker-compose.exe
Server:
ERROR: error during connect: this error may indicate that the docker daemon is not running: ...

First build failing: https://buildkite.com/elastic/elastic-package/builds/4019

Looking at the output of this step, there are also some failures related to the installation of the different packages (these failures were already present before the error mentioned above):

Failures
 - docker-engine - docker-engine not installed. The package was not found with the source(s) listed.

Failures
 - docker-cli - A newer version of docker-cli (v27.2.1) is already installed.
 Use --allow-downgrade or --force to attempt to install older versions.

Failures
 - docker-compose - A newer version of docker-compose (v2.29.3) is already installed.
 Use --allow-downgrade or --force to attempt to install older versions.

To avoid errors until these errors are solved, this step has been disabled in #2106