Conflicts:
	sbws/lib/v3bwfile.py
	tests/unit/lib/test_v3bwfile.py

in the bandwidth file to know why there excluded relays.
The excluded relays' lines do not have the `bw` KeyValue so that
Tor does not parse them nor include them in a vote.

Closes: #28563

to the bandwidth file header.

Closes: #28983.

and improve a bit the summary about what sbws does.
Closes: #29722

Part of #28565.

Part of #28565.

and return reason why the relay was excluded to be able to count
the relays excluded in the header.
Part of #28565.

Part of #28565.

if sbws is shutting down.

for the maximum number of failures before the destination is
not functional.

Part of #29589.

Closes: #29589.

Part of #29589.

Part of #28565.

Part of #28565.

and return reason why the relay was excluded to be able to count
the relays excluded in the header.
Part of #28565.

Part of #28565.

because the http server is not concurrent/asynchronous and there
are as many processes as tox environments querying the http server.

It was forgotten in #28566

Closes: #28567

and priority list counters

Part of #28567.

Part of #28567.

Part of #28567.

about the number of times it was in a priority list.
Part of #28567.

Part of #28567.

and the number of times the relay was in a priority list.
Part of #28567.

and number of times in a priority list attrs and methods,
to be able to store the data.
Part of #28567.

in the results file.

Part of #28567.

when mesuring the relay.

Part of #28567.

to store all the possible errors while measuring a relay.

It adds more technical debt, since there should be only
a ResultError class.

Part of #28567.

Since all the other bandwidth values are in bytes and sbws should
work with bytes until it generates the final `bw`.

Closes: #29707. Bugfix v1.0.3.

used in the bandwidth file, so that it is less confusing and less
prone to errors.

The total number of consensuses seen in the last days.

Part of #28566.