Fix zwave_js/node_state WS API command

[raman325]

Proposed change

As I was looking into an issue around values getting after the fact, I realized that when we get value updates, we update the Value instance data and not the Node instance data that includes a list of values when we initially loaded the node. This means that the raw node state is not accurate, and we need to combine the raw node state with the value state to get the real state of a node. This is only a problem when we get node state and not a full state dump because with the former, we are using the lib as the source, whereas with the latter we use the driver/server.

This is a bugfix but this API command is not in use yet so it can wait for the next release.

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

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

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)}}

[janiversen]

LGTM.

[MartinHjelmare]

We should think about improving the library so that we don't have stale data that can be used by mistake.

[raman325]

We should think about improving the library so that we don't have stale data that can be used by mistake.

Yeah that's on my list of items to fix. I think this is the only area where that is a problem 🤞🏾