Migrate from asar to @electron/asar

Editor assessment

The subject completely describes a package migration: the codebase moves from asar to the maintained @electron/asar fork. Both the source and destination are named, and the motivation (migrating to the scoped, maintained package) is self-evident to anyone tracking the project's ecosystem moves. The refactor type fits a dependency migration, no scope is needed, and the body's bullet about updating require calls documents the mechanical follow-through. No footers appear, and hygiene is clean. The message sets exact expectations for the diff and its ripple effects.