Use device ID as input for zwave_js WS device cmds

[raman325]

Proposed change

As discussed in home-assistant/frontend#12642 we can simplify the frontend logic by accepting device ID as input instead of config entry ID and node ID in places where the device is known already.

Dependent on home-assistant/frontend#12658

Primary changes:

• Removed ping_node WS API call because we will never use it now that we have the ping button entity
• Switched from node ID and config entry ID to device ID anywhere we are using the inputs to get a node from the driver
• Updated network_status WS API call to include node status instead just a list of node IDs. This removes a bunch of unnecessary calls to the node_status API

Type of change

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

Additional information

• Link to frontend pull request: Use device_id instead of config entry id and node id for zwave_js frontend#12658

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• 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

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this pull request as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

Thanks!