Docker Version badge producing "invalid response data" error

### Are you experiencing an issue with...

shields.io

### 🐞 Description

Recently, I've been experimenting with signing container images using cosign and SBOM generation.

Here's the workflow to doing so: https://github.com/jauderho/dockerfiles/blob/099655baac390f47854f151eab3c1da3f0396aee/.github/workflows/age.yml

This results in additional artifacts being created and uploaded to Docker Hub. See https://hub.docker.com/r/jauderho/age/tags

### 🔗 Link to the badge

Here's the link to the badge in question: https://github.com/jauderho/dockerfiles/blob/main/age/README.md

[](https://github.com/FiloSottile/age)

### 💡 Possible Solution

I believe that these artifacts are causing parsing issues resulting in the `invalid response data` seen above instead of correctly displaying the version.

Therefore, it would be great if shields.io could ignore artifacts of the form sha256-SHA256SUM.[att|sig] . Much thanks.

More background information here:
- https://github.com/docker/roadmap/issues/269#issuecomment-1026417937
- https://github.com/jauderho/dockerfiles/discussions/149

Reproduce the linked Docker Version badge using the provided image and tag, then locate the Docker badge response-parsing entry point. Done when the badge ignores the cosign and SBOM artifacts described in the issue and renders the version instead of “invalid response data”.

Written by the indexing model from the issue text.