Add custom React config panel via Module Federation

[msallin]

Mirrors the approach taken in SignalK/signalk-to-nmea0183 #154: adds a signalk-plugin-configurator keyword and a webpack-built Module Federation panel so the admin UI renders a purpose-built React form for derived-data instead of the schema-driven RJSF view. The plain plugin.schema() form is left intact as the fallback for older SK server versions.

What the panel does

• Groups all ~30 calculators by category (air, wind, depth, heading, traffic, ...) into collapsible cards
• Search input filters by calc title, optionKey, or SignalK path; matching groups auto-expand
• Per calc: enable/disable toggle and a live path-status list using Unicode glyphs from the README legend — ✅ has data, ❓ value is null, ❌ not present (refreshed every 10s from /signalk/v1/api/vessels/self)
• Per-calc extras inline: number, string, boolean, enum, plus a dedicated array-of-objects editor (used by cpa_tcpa notification zones and tankVolume calibration pairs)
• Top-level globals (default_ttl, engine/battery/tank/air_instances) live in their own card at the top
• ❗DEPRECATED calculators get a badge so they stand out

No new runtime dependencies — Unicode for icons, inline SVG for the trash button (no FontAwesome).

Screenshots

Overview (empty config, groups collapsed):

Several calcs enabled across groups with live path status:

cpa_tcpa settings expanded showing the notification-zones array editor:

Mobile (393 px):

Build wiring

• keywords adds signalk-plugin-configurator
• webpack.config.js bundles src/configpanel/PluginConfigurationPanel.tsx via ModuleFederationPlugin, sharing react/react-dom as singletons
• tsconfig.build.json excludes the panel (it compiles via ts-loader inside webpack)
• package.json adds public/ to files and build:config to prepublishOnly

How the panel discovers calcs

It fetches /skServer/plugins, locates derived-data, and walks schema.properties + uiSchema['ui:order'] to build a flat catalog. A boolean property whose title ends with the [paths] suffix is treated as a calc toggle; everything else under the same group attaches to the previous calc as "extras". This keeps the plugin's existing schema as the source of truth — no new server-side endpoints, no changes to plugin.start() or updateSchema().

Testing

• npm run typecheck clean
• npm test — 316 passing (unchanged)
• npm run build:config produces public/remoteEntry.js and chunks (~30 KiB total)
• Validated end-to-end against the upstream cr.signalk.io/signalk/signalk-server:latest image with --sample-nmea0183-data (the docker harness lives in the gitignored docker-test/ folder)

Out of scope

• Visual restyle of the path-status icons inside the existing schema description (the ❎/👍/❌ legend) — that surface is unchanged so users on older servers still get sensible RJSF output