integration-cli: fix test rogue certs

[crazy-max]

follow-up #43613 (comment)

while working on #43529, I encounter an issue with this test:

[2022-05-18T13:57:36.674Z] === Failed
[2022-05-18T13:57:36.674Z] === FAIL: amd64.integration-cli TestDockerDaemonSuite/TestHTTPSInfoRogueServerCert (0.55s)
[2022-05-18T13:57:36.674Z]     docker_cli_daemon_test.go:1407: Expected err: x509: certificate signed by unknown authority, got instead: exit status 1 and output: error during connect: Get "https://localhost:4272/v1.30/info": x509: certificate relies on legacy Common Name field, use SANs instead
[2022-05-18T13:57:36.674Z]     --- FAIL: TestDockerDaemonSuite/TestHTTPSInfoRogueServerCert (0.55s)
[2022-05-18T13:57:36.674Z] 
[2022-05-18T13:57:36.674Z] === FAIL: amd64.integration-cli TestDockerDaemonSuite (335.42s)

root cause is that the new Dockerfile now builds the docker cli for the integration tests:

moby/Dockerfile

Lines 453 to 460 in 1bf5dbb

	FROM dockercli-base AS dockercli
	RUN --mount=from=dockercli-src,src=/usr/src/dockercli/components/cli,rw \
	--mount=type=cache,target=/root/.cache \
	--mount=type=cache,target=/go/pkg/mod <<EOT
	set -e
	go build -o /out/docker -v ./cmd/docker
	xx-verify /out/docker
	EOT

previously the Dockerfile was just downloading the docker cli from download.docker.com and this one was using an old Go version that didn't have this requirement for an alt name yet. I think it's fair to update the rogue certs as in the future we are going to have the exact same issue anyway.

cc @thaJeztah

Signed-off-by: CrazyMax crazy-max@users.noreply.github.com

[thaJeztah]

LGTM (if green) 👍