refactor(electron): delete v1 lazy-extension command machinery
CONSOLIDATED_EXTENSION_IDS, registerLazyExtensionCommands,
registerLazyCommand, registerLazyEventInterceptors,
handleLazyExtensionReady, getExpectedCommandTopics, lazyExtensionLoaded
+ companion Maps were a parallel v1 mechanism doing what the v2
tile-lazy.ts pre-publish dispatch hook now handles for every tile in
the list (all 19 IDs are manifestVersion 3 tiles already). The list
was a hardcoded allowlist that v2 derives from `lazy: true` /
`resident: true` manifest flags via tile-compat.
Rename EAGER_EXTENSION_IDS → EAGER_TILE_IDS (still used by
initializeFeatures' v2 path). Drop unused `unsubscribe` and
`hasSubscriber` imports; ManifestCommand stays for the still-live
declarative-only path (background:false manifests).
Also delete lazy-loading.test.ts — it simulated the deleted v1
buffering pattern with hand-rolled subscribe/publish; tile-lazy has
its own test coverage (tile-lazy-events.test.ts,
tile-command-registration.test.ts, tile-lazy-timeout.test.ts).