Bump zwave-js-server-python to 0.55.1

[raman325]

Proposed change

Changelogs:

• https://github.com/home-assistant-libs/zwave-js-server-python/releases/tag/0.55.0
• https://github.com/home-assistant-libs/zwave-js-server-python/releases/tag/0.55.1

Main changes:

• uses orjson when available
• Adds additional information to the initial state dump for rebuilding routes so we can display route information more quickly
• Adds some additional CC constants @TastyPi
• Adds some missing value metadata properties, one of which is needed for certification
• Revert breaking change that was not needed

home-assistant/addons#3351 must be merged first EDIT: This is no longer true even though it was merged already

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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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 pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[MartinHjelmare]

We've talked about that we should not label these PRs as breaking, but maybe we should still do that until the repair issue description is more detailed about what version is required and what the user needs to do. I had a suggestion that we should link the user to the github release they need, depending on how they run the server.

[raman325]

thanks for the reminder, I will create an issue in the lib repo so we don't forget to work on that. Outside of OS, can we know how they run the server? I don't think we collect that information. Might be worth an enhancement of some sort though

[raman325]

I think we should go straight to 0.55.1 to avoid the breaking change so will mark this as draft until we have the patch version released

scope change

[raman325]

coverage failures are unrelated to this PR