Add new zwave_js WS command to parse DSK from QR code

[raman325]

Proposed change

Updates the zwave_js integration to support features introduced in zwave-js 10.4.0 and zwave-js-server-python 0.45.0:

• Adds try_parse_dsk_from_qr_code_string API command which allows users to scan a DSK QR code. This just adds support for more provisioning methods

To implement this in the frontend, we need to:

• Add support for this command
• run each QR code through this command before checking for length and that it starts with 90 and trying to parse QR code information from it, and if it returns something other than null, provision the node using S2 security and the dsk parameter option

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)
• Deprecation (breaking change to happen in the future)
• 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.

To help with the load of incoming pull requests:

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

[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!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.

[raman325]

there's an open question in #devs_zwave if we can do the same validation on the QR Code string as we do for the QRProvisioningInformation. Depending on the answer this PR may need to be adjusted

EDIT: Per @AlCalzone we do not need to do any upfront validation for the DSK check, we should just send it to the function which will do the validation for us.

[AlCalzone]

yep, if the method doesn't return a DSK, the QR code is not a DSK-only QR and the existing logic applies.

[MartinHjelmare]

We should wait with merging here until there's a linked and approved frontend PR.