chore(publish.sh) fix publication check by switching from raw curl to docker buildx imagetools for stronger manifest retrieving

[dduportal]

The PR #1558 aimed at fixing the publication process by decreasing the amount of checked platform.

But this was not enough as only the past 3 weekly where checked, so b9e129d fixed it by checking the 2 last LTS and the 2 last weekly in order to unblock the 2.375.3 LTS release.

This new PR aims at fixing the root cause which is the Docker buildx + DockerHub switching to OCI images (including OCI manifest) instead of the former Docker custom manifests.

Found the error message `` which pointed me to jjlin/docker-image-extract#2.

This change, announced in https://www.docker.com/blog/announcing-docker-hub-oci-artifacts-support/, was not seen as breaking but it was in fact.

By switching out from curl requests to the DockerHub API (which is fragile code) to the docker buildx imagetools command line:

• It's a bit slower (acceptable since we only check 4 tags, not 30 as before)
• It does not require an anonymous token (reuses the current Docker engine)
• It's stronger for change as it will always delegate the manifest analysis to docker CLI internals

[dduportal]

Post merge: the publication step on trusted.ci shows the following output with this change:

# ...
[2023-02-08T17:59:16.496Z] + make publish
[2023-02-08T17:59:16.496Z] ./.ci/publish.sh
[2023-02-08T17:59:16.760Z] Docker repository in Use:
[2023-02-08T17:59:16.760Z] * JENKINS_REPO: jenkins/jenkins
[2023-02-08T17:59:20.987Z] Tag is already published: 2.389
[2023-02-08T17:59:24.295Z] Tag is already published: 2.390
[2023-02-08T17:59:28.506Z] Tag is already published: 2.375.2
[2023-02-08T17:59:43.425Z] Tag is already published: 2.375.3

=> LGTM.