Describe the bug
The version checker does not pick up the latest image tag from ACR.
By default, it picks the highest number in ACR as the latest one (first row on the screenshot). If we add annotations like
enable.version-checker.io/my-container: "true" and use-sha.version-checker.io/my-container: "true" or match-regex.version-checker.io/my-container: ^\d+\.\d+\.\d+$ shows the proper version according to the sem version but not the latest one (see the second row on the screenshot).
image

These two images' metadata:
Not latest one:
image
The latest one:
image

To Reproduce
Steps to reproduce the behavior:

1. Deploy version-checker 0.8.5
2. Set up the connection to the ACR
3. Annotate Pods with enable.version-checker.io/my-container: "true" and use-sha.version-checker.io/my-container: "true" or match-regex.version-checker.io/my-container: ^\d+\.\d+\.\d+$
4. Set up the Grafana Dashboard
5. See the wrong latest image for pod.

Expected behavior
The version-checker picks the latest image by number according to the sem version or sha based on modify date.

Environment (please complete the following information):

• Version-Checker: 0.8.5
• Kubernetes: 1.29.4
• Grafana: 10.0.1
• Victoria Metrics: 1.93.1