Traffictoll

Added support for setting a fixed global traffic priority, allowing to invert the whitelist/blacklist behavior for traffic prioritization. Now it is possible to adjust the global traffic to a high priority for example, and define a single process with a lower priority instead of having to capture all important traffic in processes and adjust their priority.

Also, provided either the [Speedtest CLI by Ookla](https://www.speedtest.net/apps/cli) or [speedtest-cli by sivel](https://github.com/sivel/speedtest-cli) is in PATH, you can use `--speed-test` or `-s` when starting TrafficToll to automatically determine the download and upload speed in case you want to make use of traffic prioritization. Please note that you have to run `speedtest --accept-license` as root (because TrafficToll will run speedtest as root), if you are using the Ookla version, before you can use it.

The equivalent to "committed" rates in FireQOS. These are the rates that classes are guaranteed when they are otherwise starved of bandwidth by classes with higher priority. Before it was 1bps (8 bits per second), the minimum rate that can be specified, but this caused other IPs to drop the connections because they assumed the connection died.

The process sections now support a "recursive" keyword which can be set to a boolean. This is useful if you want to traffic-shape a matched process' descendants' connections.

Support for traffic prioritization, see issue 6. Each process section now supports 2 new keys: "upload-priority" and "download-priority". 0 is the highest with higher integers representing a lower priority. There's a new "example.yaml" config which is bundled with the source release and copied verbatim into the README.