feat: COM + toast notification activation in generated AppxManifest

[bitdisaster]

Summary

Adds optional manifestVariables.comToastActivation so generated manifests can declare the packaged COM server (windows.comServer) and toast notification activation (windows.toastNotificationActivation) used by desktop apps for toast click handling, aligned with Microsoft’s packaged desktop toast guidance.
Only applies when the manifest is generated (no appManifest); pre-built manifests are unchanged.

What’s included

• static/templates/ComToastActivation.xml.in – Fragment for <Extensions> under <Application> (com:Extension + desktop:Extension).
• src/manifestation.ts – Merges fragment into the main template; xmlns:com stays in code; IgnorableNamespaces gains com and desktop when toast activation is enabled.
• ComToastActivationOptions (types.ts): toastActivatorClsid (required), optional arguments (default -ToastActivated), optional executable (basename; path in manifest is app\{executable}).
• CLSID normalization – Single normalizeToastActivatorClsid(raw, braced?): default braced {guid}; braced: false for manifest (no braces, per MakeAppx/schema).
• verifyOptions – Validates toastActivatorClsid as a GUID when set.
• Exports – ComToastActivationOptions re-exported from src/index.ts.
• Tests – Unit coverage for manifest generation, GUID validation, and normalizeToastActivatorClsid; e2e packages with comToastActivation and asserts manifest content via readAppxManifestFromMsix in test/e2e/utils/installer.ts.
• README – Documents comToastActivation and example usage.

Notes

• Template omits optional DisplayName attributes on ExeServer / Class to match minimal manifest samples.

How to verify

npm run test:unit
npm run test:e2e