Zip CLI artifacts directory for release attachments

[Copilot]

The GitHub release workflow needed a reliable way to attach all CLI artifacts from multiple platforms to releases.

Changes

• Zip the ./artifacts_download directory into cli-artifacts.zip before creating releases
• Updated gh release create commands in both Github release and Github prerelease steps to attach the zip file
• Added shell: bash to Github release step for consistency

This ensures all CLI artifacts in nested directories under ./artifacts_download/ are properly captured in a single zip file:

# Create zip of all artifacts
zip -r cli-artifacts.zip ./artifacts_download
gh release create $VERSION ./SkiaSharpCompare/bin/Release/*.*nupkg cli-artifacts.zip --generate-notes

The zip file approach is simpler and more reliable than glob pattern expansion, and provides users with a convenient single download containing all platform-specific CLI binaries.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[stesee]

@copilot stop fiddling with lobster
Zip the directory that is tried to use in gh release

[Copilot]

@copilot stop fiddling with lobster
Zip the directory that is tried to use in gh release

Changed to zip the artifacts directory instead. The workflow now creates cli-artifacts.zip from ./artifacts_download and attaches it to releases. Commit 33b6b5f.