fix: move git tag creation before package build for MinVer

The workflow was creating the git tag AFTER building NuGet packages,
but MinVer needs the tag to exist BEFORE the build to calculate the
correct version. This was causing packages to be versioned as
2.0.1-alpha.0.2 instead of 3.0.0.

Changes:
- Moved "Create tag" step to execute after "Update version" and before "Restore dependencies"
- Now the v3.0.0 tag exists when dotnet pack runs
- MinVer will detect the tag and create packages with version 3.0.0

This fixes the NuGet package publishing issue for v3.0.0.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: phmatray

.github/workflows/ci-cd.yml

@@ -119,7 +119,14 @@ jobs:
             sed -i "s|<Version>.*</Version>|<Version>${VERSION}</Version>|g" "$file"
           fi
         done
-    
+
+    - name: Create tag
+      if: steps.should_release.outputs.new_release == 'true'
+      uses: mathieudutour/github-tag-action@v6.2
+      with:
+        github_token: ${{ secrets.GITHUB_TOKEN }}
+        custom_tag: ${{ steps.get_version.outputs.new_version }}
+
     - name: Restore dependencies
       if: steps.should_release.outputs.new_release == 'true'
       run: dotnet restore
@@ -165,14 +172,7 @@ jobs:
         github-token: ${{ secrets.GITHUB_TOKEN }}
         skip-commit: true
         output-file: false
-    
-    - name: Create tag
-      if: steps.should_release.outputs.new_release == 'true'
-      uses: mathieudutour/github-tag-action@v6.2
-      with:
-        github_token: ${{ secrets.GITHUB_TOKEN }}
-        custom_tag: ${{ steps.get_version.outputs.new_version }}
-    
+
     - name: Push to NuGet
       if: steps.should_release.outputs.new_release == 'true'
       run: |