Publish full YYYY.MINOR.PATCH Docker tags for .0 OVMS releases

Summary

Please publish full three-component Docker tag aliases for OVMS releases
whose patch component is zero.

For example, OpenVINO Model Server 2026.3.0 currently publishes:

• openvino/model_server:2026.3
• openvino/model_server:2026.3-gpu

Please additionally publish:

• openvino/model_server:2026.3.0
• openvino/model_server:2026.3.0-gpu

Existing short tags should remain available for backward compatibility.

Motivation

Patch releases already use three-component tags, for example:

• 2026.2.1
• 2026.2.1-gpu

Consequently, consumers must alternate between two- and three-component
version tags when pinning exact releases:

• 2026.2.1-gpu
• 2026.3-gpu
• potentially 2026.3.1-gpu

This causes compatibility problems for update-monitoring and dependency
automation that compares tags with consistent numeric precision. It also
makes the Docker tag differ from the full version shown in the release
title, which is 2026.3.0.

Publishing full .0 aliases would provide a canonical exact-version tag
for every release while preserving the existing short aliases and
latest channels.

Expected result

Every stable release has an immutable full-version Docker tag:

• YYYY.MINOR.0[-gpu] for the initial release
• YYYY.MINOR.PATCH[-gpu] for subsequent patches

Short YYYY.MINOR[-gpu] aliases may continue to be published unchanged.

Locate the repository's Docker image publishing workflow and inspect how version tags and GPU variants are generated for stable releases. Verify the change preserves short aliases and latest channels while adding immutable full-version tags for initial and subsequent releases, then run the repository's relevant release or container validation checks.