Upgrade asar to a version that requires Node 10

Editor assessment

The subject states both the change and its consequence: asar is upgraded to a version requiring Node 10. The dependency, the direction, and the new constraint are all named, which is more informative than a bare version bump because it flags the toolchain implication. The build type fits dependency management, no scope is needed, and the body's two squash bullets trace the intermediate version targets without confusion. No footers appear, and hygiene is clean. The message communicates the upgrade, its runtime requirement, and its progression accurately and compactly.