python3Packages.plugwise: 0.9.3 -> 0.9.4

[fabaff]

Motivation for this change

Update to latest upstream release 0.9.4

Change log: https://github.com/plugwise/python-plugwise/releases/tag/0.9.4

Incl. cleaning up and Home Assistant test.

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[r-rmcgibbo]

Result of nixpkgs-review pr 121960 at eceb958f run on aarch64-linux 1

1 package failed to build:

• home-assistant

2 packages built successfully:

• python38Packages.plugwise
• python39Packages.plugwise

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

---

Result of nixpkgs-review pr 121960 at eceb958f run on x86_64-linux 1

1 package failed to build:

• home-assistant

2 packages built successfully:

• python38Packages.plugwise
• python39Packages.plugwise

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

[mweinelt]

Apparently needed in propagatedBuildinputs, as imports are failing in the home-assistant test run.

[mweinelt]

Okay, jsonpickle is in requirements_test.txt, I wish we could also have test dependencies autogenerated from the manifest, but there does not seem to be a field for that upstream and the requirements_test.txt is tracked manually.