bug(quake): SemVer build metadata can bypass image-version compatibility handling

[huklaa]

Summary

Quake image-version parsing can treat valid SemVer tags containing build metadata, such as v0.4.0+build.1, as unparsable. The fallback path can then assume CLI flag compatibility instead of applying the version-specific compatibility rewrite.

This is the issue-backed continuation of PR #278, which was closed because it predated the current issue/assignment policy, not because the change was rejected technically.

Expected behavior

Valid prerelease/build metadata must not prevent MAJOR.MINOR.PATCH from being parsed for compatibility decisions.

Existing implementation

PR #278 already contains:

• the focused parser fix
• regression coverage around the v0.5.0 / v0.6.0 compatibility boundaries
• prerelease + build metadata cases

The earlier PR received detailed technical review and was considered sound pending CI.

Under the current contribution policy, I am requesting assignment here before opening any replacement PR.

Please assign this issue to @huklaa if maintainers want the existing fix resubmitted.

[romac]

Thanks for the report. The parser does not handle SemVer build metadata, but + is not valid in a Docker/OCI image tag, and Quake
uses this value as the image tag. This path is therefore not reachable with a valid image reference, so we are closing it as not
applicable. Please reopen with a reachable example if we missed one.