AlCalzone

TODO: - [ ] get rid of `@ts-expect-error` directives - [ ] changelog - [x] remove `info.healingNetwork` state on startup - [x] go through v11 [migration guide](https://zwave-js.github.io/node-zwave-js/#/getting-started/migrating-to-v11) - [x] go...

Some deps use `node:` imports, those are supported in Node.js starting: v16.0.0, v14.18.0 (ESM import and CommonJS require())

Take a look at force directed graph

1

https://blockbuilder.org/muzy/d1b7ef91c71d76ca831b81f497d878d4

There are several features we need to add support for: - [ ] `getFirmwareUpdateCapabilities` - [ ] querying user codes on demand - [x] Statistics (https://github.com/AlCalzone/ioBroker.zwave2/pull/709) - [x] Multicast (https://github.com/AlCalzone/ioBroker.zwave2/pull/708)...

https://github.com/Microsoft/TypeScript/issues/29226

With this PR, package.json, io-package.json and the README/CHANGELOG files are reset to the previous status if the release script aborts, e.g. due to a failed translation. fixes: #126