[Feature]: Provide OpenLogi via Chocolatey (Windows package manager)

### Pre-flight checklist

- [x] I searched existing issues and the [Roadmap](https://github.com/AprilNEA/OpenLogi#roadmap), and this isn't already tracked.

### Problem / motivation

Currently OpenLogi on Windows is distributed only as .msi installers attached to each GitHub release. There's no way to install or update OpenLogi through a package manager on Windows, which makes it harder to manage on machines that are already administered via Chocolatey (e.g. in scripted provisioning, Ansible/DSC-based Windows fleets, or simple `choco upgrade all` maintenance routines).

### Proposed solution

Publish an official OpenLogi package on the Chocolatey Community Repository (or as a Chocolatey package hosted alongside the existing release artifacts), so that installation and updates can be done via:

```powershell
choco install openlogi
choco upgrade openlogi
```

The package should:
- Wrap the existing signed .msi installer (x86_64 and arm64) already published per release
- Support Chocolatey's standard silent-install arguments so it works in unattended/automated deployments
- Be kept in sync with the GitHub release cadence (ideally automated via the existing release workflow, similar to how the Homebrew cask is already auto-bumped)

### Alternatives considered

- Manual download and installation of the .msi from the releases page — works, but doesn't integrate with existing package-manager-based update/maintenance workflows.
- Winget — could be a parallel option, but Chocolatey is specifically requested here due to existing tooling already in use.

### Related area(s)

- [ ] GUI
- [ ] CLI
- [ ] Button actions / remapping
- [ ] DPI
- [ ] SmartShift
- [ ] Per-application profiles
- [ ] Configuration (TOML)
- [x] Auto-update
- [x] Other

### Additional context

OpenLogi already maintains an official Homebrew cask for macOS with automated version bumps. A Chocolatey package would bring Windows installation/update workflows to parity with macOS, and would fit naturally into the existing CI/release pipeline (e.g. as an additional step in the GitHub Actions release workflow that pushes a new package version to Chocolatey whenever a new release is published).

Start by inspecting the existing GitHub Actions release workflow and the Homebrew cask automation referenced in the issue, then review the signed x86_64 and arm64 MSI release artifacts. Done means an official Chocolatey package supports silent installation and upgrade, and new GitHub releases keep the package version synchronized.

Written by the indexing model from the issue text.