fix: update release workflow to build and attach Windows EXE instead …

[Andx667]

This pull request updates the release workflow to change the Windows release artifact from an MSIX installer to a versioned standalone EXE file. The workflow and related steps have been renamed and adjusted to build, prepare, and attach the EXE file instead of the MSIX package.

Release workflow updates:

• The workflow name was changed to "Release APK and Windows EXE" to reflect the new artifacts being published.
• The Windows job was renamed from build-windows-msix to build-windows-exe to match the artifact type.

Windows release artifact changes:

• The MSIX build and packaging steps were removed and replaced with steps to prepare a versioned Windows EXE filename, copy the built EXE, and output its path.
• The release upload step now attaches the EXE file instead of the MSIX installer, updating both the step name and the file reference.

[Copilot]

Pull request overview

This PR updates the release workflow to publish a Windows EXE artifact instead of an MSIX installer, aligning the workflow/job naming with the new intended release artifact.

Changes:

• Renames the release workflow and Windows job to reference Windows EXE output.
• Replaces MSIX packaging with copying a versioned Windows executable.
• Updates the release upload step to attach the EXE path.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/release.yml	Changes Windows release packaging/upload from MSIX to a versioned EXE artifact.
pubspec.lock	Updates transitive dependency lock entries for meta and test_api.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.