fix(docker): use a HEAD request to the real resource auth.

[vlagorce]

Changes

When listing tags we should make a HEAD request to the real resource and use the auth header values to get a token

Context

Closes #14708

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

Mistaken package.json change?

[vlagorce]

Mistaken package.json change?

removed.

[viceice]

I think this needs some real runs against different docker registries 🤔

[vlagorce]

Folowing your mesage I ran this branch against a repo having images hosted in ACR.
Updates are found without any lookup error. :)

[renovate-release]

🎉 This PR is included in version 32.12.1 🎉

The release is available on:

• GitHub release
• 32.12.1

Your semantic-release bot 📦🚀

[rslinckx]

Might this have caused the following errors on gcr.io (and also on eu.gcr.io) since 2 days?:

WARN: Invalid registry response
{
  "apiCheckUrl": "https://gcr.io/v2/datadoghq/cluster-agent/tags/list?n=10000",
  "res": {
    "statusCode": 405,
    "body": "",
    "headers": {
      "docker-distribution-api-version": "registry/2.0",
      "content-type": "application/json",
      "content-encoding": "gzip",
      "date": "Fri, 08 Apr 2022 07:47:28 GMT",
      "server": "Docker Registry",
      "cache-control": "private",
      "x-xss-protection": "0",
      "x-frame-options": "SAMEORIGIN",
      "transfer-encoding": "chunked",
      "alt-svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000,h3-Q050=\":443\"; ma=2592000,h3-Q046=\":443\"; ma=2592000,h3-Q043=\":443\"; ma=2592000,quic=\":443\"; ma=2592000; v=\"46,43\"",
      "connection": "close"
    },
    "authorization": false
  }
}
DEBUG: Failed to get authHeaders for getTags lookup