bandwhich: init at 0.6.0

Currently if you specify home to be someplace else than ~/ for user
then Transmissions always attempts to load the config from the
default location which is $HOME/.config/transmission-daemon based on documentation:
https://github.com/transmission/transmission/wiki/Configuration-Files



Which means that the changes done to the config under settingsDir in
ExecPreStart have no effect because they are modifying a file that is never loaded.

I've added an explicit --config-dir ${settingsDir} to make sure
that Transmission loads the correct config file even when home is changed.

Signed-off-by: Jakub Sokołowski <jakub@status.im>

qbittorrent: 4.2.0 -> 4.2.1

nixos/containers: use machinectl poweroff

nextcloud module: https is important not only for proxies

rambox: fix hash

linuxPackagesFor: wireguard: respect supported kernel versions

wpsoffice: update `src`

- Rename from `what` to `bandwhich`
- Add Security for darwin

gcc-arm-embedded: 8-2019-q3-update -> 9-2019-q4-major

stdenv, haskell: bonafied GHCJS cross compilation without stdenv.cc

Previously, we were storing the leader pid in a runtime file and
signalled SIGRTMIN+4 manually.

In systemd 219, the `machinectl poweroff` command was introduced, which
does that for us.

nagios: various improvements

gradle: 5.6.1 -> 5.6.4

Bochs: quote homepage URL in order to suit the new standards

shorewall: init at 5.2.3.3

nixos/shorewall: init

python3Packages.fsspec: 0.5.2 -> 0.6.2 enable tests

Packaging several async python web libraries / databases connectors

Fix build and update dpdk and dependent packages

Building with make requires share/dpdk/mk/ from the make build of dpdk, which is
not installed by the meson build of dpdk.