Use device_id instead of config entry id and node id for zwave_js

[raman325]

Proposed change

Instead of using config entry ID and node ID for any device specific WS commands, we now use device_id. This replaces #12642

Fixes #12641
Fixes #12136
Dependent on home-assistant/core#71667

Primary changes:

• Got rid of dependencies on config entry ID and node ID where possible so we can just pass the device ID into the WS commands which is already available on these pages
• Updated the network_status WS API command to return the node statuses instead of a list of node IDs so that we can save an API call

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• Link to core pull request: Use device ID as input for zwave_js WS device cmds core#71667

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[raman325]

The related core PR has been approved

[bramkragten]

Do we still need entry_id here, can't we also make that work with device id?

[raman325]

the entry ID is still needed by dialog-zwave_js-heal-node so that it can get the network status here:

frontend/src/panels/config/integrations/integration-panels/zwave_js/dialog-zwave_js-heal-node.ts

Lines 205 to 208 in bbe9dc6

	const network: ZWaveJSNetwork = await fetchZwaveNetworkStatus(
	this.hass!,
	this.entry_id!
	);

We can pass just the device ID in and derive the entry ID in dialog-zwave_js-heal-node but we currently already have to figure out entry ID in ha-device-actions-zwave_js so that we can add it to the URL, so why recalculate it? Is it necessary to add it to the URL though? I couldn't figure out why we do that, and if it's not necessary, we can just pass the device ID in and only calculate entry ID in the heal node dialog

[raman325]

another alternative would be to allow fetchZwaveNetworkStatus to accept either an entry ID or a device ID since it's used in both contexts. This could easily be supported in the core

[bramkragten]

Sounds like the nicest approach

[bramkragten]

Want to merge this and do that in a new PR?

[raman325]

good idea