fix(factories): refetch on profile switch + add activeProfileId to route deps

[8144225309]

Problem

Switching the wallet's active node via the NodePicker dropdown could leave the Factories list empty even though the new node's plugin had factories — surfaced during the post-#46 orchestrator audit (tracked as bug #157).

The audit reproduced it deterministically:

• Active profile = ss-demo-lsp on /bookkeeper
• Switch dropdown → ss-demo-client
• Navigate to /factories
• Wallet shows All=0 / LSP=0 / Client=0

Meanwhile CLI factory-list on the client returned 3 factories (e2ebf4f0, d607, a823931a), and the Dashboard correctly showed 1 channel from the client POV (confirming backend rebinding worked).

Root cause

Two cooperating bugs in the post-switch / route-data plumbing:

1. NodePicker.handleSwitchNode (apps/frontend/src/components/ui/NodePicker/NodePicker.tsx:63-73)
   The background refresh after a profile switch fetched only one section's data, chosen by the current pathname:

   const bgRefresh = pathname.includes('/bookkeeper')
     ? BookkeeperService.fetchBKPRData()
     : pathname.includes('/factories')
       ? FactoriesService.fetchFactoriesData()
       : CLNService.fetchCLNData();

   Switch profile on /bookkeeper → only BKPR refetched, factories left empty.

2. routerReduxSync.tsx:118 — the route-data effect's deps were [authStatus, pathname, navigate]. activeProfileId was missing, so a profile change without a pathname change didn't re-fire the effect.

Together: switching on one section and navigating to another sometimes didn't refresh — depending on timing — leaving stale or empty data.

Fix

1. NodePicker — handleSwitchNode eagerly refetches CLN, BKPR and Factories in parallel on every profile switch, regardless of current pathname. Fire-and-forget so switch UX stays snappy, but downstream views always have data ready for the new profile.

2. routerReduxSync — adds activeProfileId to the route-fetch effect deps + imports selectActiveProfileId. Now an active-node change re-runs the current route's data fetch against the new node.

Also drops the unused useLocation import from NodePicker (the pathname-conditional bgRefresh is gone).

Verification

CI build/eslint/test. Empirical verification on the demo wallet after deploy: switch dropdown LSP↔Client and the factories list re-populates with the correct per-node view.