feat: support otw update

[robertsLando]

No description provided.

[robertsLando]

cc @AlCalzone

[coveralls]

Pull Request Test Coverage Report for Build 3939487789

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 172 (0.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.2%) to 24.086%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/stores/base.js	0	11	0.0%
lib/ZwaveClient.ts	0	161	0.0%

Totals
Change from base Build 3938205728:	-0.2%
Covered Lines:	3784
Relevant Lines:	16597

---

💛 - Coveralls

[AlCalzone]

I'm missing a BIG FAT WARNING here:

If a user uploads the wrong file, the controller can be bricked. 700 series may be recoverable via the bootloader, see also https://zwave-js.github.io/node-zwave-js/#/api/driver?id=driver-events.
500 series is likely gone if the wrong file gets uploaded.

Also it would be good if the bootloader/fallback mode of the controller could be exposed - maybe in a separate PR though. See https://zwave-js.github.io/node-zwave-js/#/api/driver?id=zwaveoptions -> allowBootloaderOnly description.

[AlCalzone]

Testing result:
I didn't see any progress and the update seems to have been done with an empty file, so nothing actually got uploaded.