Implement dual package system to reduce update download size from 60MB to 0.5MB

[Copilot]

This PR addresses the issue where updates required downloading 60+ MB instead of the desired 0.5MB by implementing a dual package build system.

Problem

The previous fix in PR #1 introduced self-contained .NET publishing which bundles the entire .NET runtime (~60MB) into every artifact. While this solved deployment issues, it created a new problem: users downloading updates had to download the full 67.5MB package even when they already had .NET installed.

Solution

Created two distinct build outputs to serve different use cases:

Full Install Package (~60MB)

• Purpose: Clean installations for new users
• Configuration: --self-contained true with complete .NET runtime
• Artifact name: full-install
• Requirements: None - runs on any Windows system
• Use case: First-time installations or systems without .NET 8

Update Package (~0.5MB)

• Purpose: Updates for existing installations
• Configuration: --self-contained false (framework-dependent)
• Artifact name: update-package
• Requirements: .NET 8 runtime pre-installed
• Use case: Updates for users who already have the runtime

Key Changes

GitHub Actions Workflow:

• Split the single publish step into two parallel builds
• Created separate artifact uploads with descriptive names
• Added comprehensive size reporting and download instructions
• Enhanced error handling and validation

Documentation:

• Updated README with clear installation instructions for both packages
• Added comparison table showing sizes, requirements, and use cases
• Included .NET runtime installation guidance
• Explained the 120x size reduction benefit for updates

Impact

• Solves the core issue: Updates are now 0.5MB instead of 60+MB
• Maintains compatibility: Full install option preserves existing functionality
• Improves user experience: Clear choice between packages based on needs
• Saves bandwidth: 120x reduction in download size for updates
• Future-proof: Sustainable approach for ongoing updates

Users can now choose the appropriate package for their situation, dramatically reducing download times and bandwidth usage for updates while maintaining the reliability of self-contained installations for new users.

Fixes #2.

---

💡 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.

[Copilot]

@lsd-techno 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.