fix: use version in Docker artifact naming for consistency with NPM (#311)

Changed Docker artifact-name from 'docker-image-${{ github.sha }}' to
'docker-image-${{ needs.build.outputs.version }}' to match the NPM
artifact naming pattern.

This ensures consistent artifact naming across all artifact types:
- NPM: npm-package-{VERSION}-{SHA}
- Docker: docker-image-{VERSION}-{SHA}

With consistent naming, determine-artifact.sh can use the same logic
for both artifact types without conditional branches.

Fixes the publish workflow failures where it couldn't find Docker
artifacts because it was looking for docker-image-{VERSION}-{SHA}
but the actual artifact was docker-image-{SHA}-{SHA}.

Author: sapientpants

.changeset/fix-docker-artifact-naming.md

@@ -0,0 +1,7 @@
+---
+'sonarqube-mcp-server': patch
+---
+
+Fix Docker artifact naming to match NPM pattern for consistent artifact resolution
+
+Changed Docker artifact naming from `docker-image-{SHA}` to `docker-image-{VERSION}` to match the NPM artifact pattern. This ensures the determine-artifact.sh script can find Docker artifacts using the same logic as NPM artifacts, eliminating the need for conditional logic based on artifact type.

.github/workflows/main.yml

@@ -188,7 +188,7 @@ jobs:
     with:
       platforms: 'linux/amd64,linux/arm64'
       save-artifact: true
-      artifact-name: 'docker-image-${{ github.sha }}'
+      artifact-name: 'docker-image-${{ needs.build.outputs.version }}'
       image-name: 'sonarqube-mcp-server'
       version: ${{ needs.build.outputs.version }}
       tag_sha: ${{ github.sha }}