Handle breaking changes as result of zwave_js lib upgrade

[raman325]

Proposed change

In home-assistant/core#100833 we are bumping zwave-js-server-python which handles Z-Wave JS v12.x. As part of this change, healing was renamed to rebuilding routes. I have therefore updated all of the function names, strings, etc. to use the new language.

Type of change

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

Example configuration

Additional information

• Link to core pull request: Bump zwave-js-server-python to 0.52.0 core#100833
• Link to documentation pull request: Document zwave_js changes for lib bump to 0.52.0 home-assistant.io#29036

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• 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