Add get_config_parameters websocket command to zwave_js

[cgarwood]

Proposed change

Adds a get_config_parameters websocket command to the zwave_js integration. Will be used for the frontend config panel.

Will require a new release of the upstream zwave-js-server-python library.

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.
• 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 its been labeled with an integration (zwave_js) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[raman325]

aside from my comments, looks good! Just keep in mind that we can't set all configuration values, so we will need some handling for that when we add support for it. If nothing else it could be as simple as catching the exception that will get raised when calling async_set_value

[cgarwood]

Marking as draft until upstream lib gets bumped

[raman325]

LGTM once tests pass!

[cgarwood]

Just waiting for a new release of the lib 🙂

[raman325]

this needs a rebase then it should hopefully be good to go

[raman325]

should this be renamed get_config_parameters to match the service?

[raman325]

I added a commit to #46673 to include a set_config_parameter WS API command

[MartinHjelmare]

There are unrelated commits.

[cgarwood]

aaaah rebase failure

[cgarwood]

OK fixed the rebase disaster

[raman325]

I think we can mark this Ready for review?

[raman325]

re-approving since there were some changes, but it looks good!

[MartinHjelmare]

Looks good!