They were used to resolve the IP of the destination and check
whether an exit policy allows to exit to that IP, but when the
destination is a CDN, the IP locally resolved would be different
to the IP resolved in the exit, and when the IP resolved to
IPv6, it was possible that the scanner didn't have IPv6.
The correct method to check whether an exit policy allows to exit
to an IP, would be to resolve the domain via Tor itself using
RESOLVE and ADDRMAP events with that exit.

The flags are: not having a badflag and the policy allows to exit
to a port.

The flags are: not have the badflag and the policy allows to exit
to a port.

The flags are: not having a badexit and the policy allows to exit
to a port.

In order to do not relay on resolving a domain locally to check
the IP in the exit policy.

Even if that method is call from generate with torflow's scaling
by default.

So that is less confusing that it's the default.
We already have an option for linear scaling and no scaling.

Continue running with defaults when the config argument is provided
but not found. This could be the case of system packages.

sbws is getting a significant number of build failures due to keyserver failures.

Using the high-availability keyserver pool reduces the probability of failure.

Implements part of proposal 276.

Implements 28451.

Part of 28442.

And add unit tests for rounding and rounding error.

Bugfix on 27337 in sbws 1.0.

Part of 28442.

Include the headers about eligible relays in all the bandwidth
files, not only in the ones that does not have enough eligible
relays (#28365).

Since they depende only on the mayor number

Instead of comparing all the version.

Since 1.0.0 is now reached.