[BUG] Node-RED Add-on persistently installs 'node-red-dashboard' (V1), causing conflict with FlowFuse Dashboard (V2)

[UserBRMFC]

The Node-RED Add-on automatically installs node-red-dashboard (V3.6.5, V1) as a base dependency, even after clean re-installations and explicit configuration to use the new FlowFuse Dashboard (@flowfuse/node-red-dashboard, V2). This V1 module starts and claims the /ui route, preventing V2 from initializing correctly, leading to the "Welcome to the Node-RED Dashboard" message when viewing the actual V2 dashboard page.

This is a structural conflict that cannot be resolved via user-level configuration (npm_packages or init_commands).

Steps Taken & Evidence

1. Clean Installation: The Node-RED Add-on was completely removed and re-installed.
2. Explicit Configuration: The Add-on configuration was explicitly set to install V2 and omit V1.

YAML

npm_packages:

• node-red-contrib-home-assistant-websocket@0.61.1
• @flowfuse/node-red-dashboard

3. Issue: Despite the above, V1 is still installed and starts. The log shows:

[info] Dashboard version 3.6.5 started at /endpoint/ui

4. Workaround Failure: I attempted to force the uninstallation of V1 using init_commands, which failed because the
   YAML parser in the Add-on removes necessary quotes, causing the shell command to fail. (I later used the sh -c wrapper
   as a final attempt, but the module still loads first).

The attempted workaround in init_commands:
YAML

init_commands:

• 'npm uninstall node-red-dashboard --prefix /config'

Expected Behavior
Since node-red-dashboard is not explicitly listed in npm_packages, the Add-on should not install it.

Or, the Add-on should offer an explicit configuration option (e.g., install_v1_dashboard: false) to disable the hardcoded installation of the V1 module, allowing V2 to start without conflict.

Environment
Add-on version: 20.0.0
System: Home Assistant OS 16.2
Hardware: Raspberry Pi 4 (aarch64)