- Create new KeyValues constants for the new v1.5.0 KeyValues
- Instanciate State in Header.from_results so that there is no need
  to create new methods for all the header KeyValues that are read
  from the state file
- Add tor_version to the kwargs to initialize the Header
- Write tor_version in the state file when the scanner is started

Closes: #30196.

Rename constants to make their names more consistent with each other.
All header constants start now by HEADER_ and all Bandwidth Lines by
BWLINE_.
The constants that are a list of keys are now named KEYS instead of
KEY_VALUE or KEY_VALUE.

These are the substitutions made:

s/BW_KEYVALUE_SEP_V1/BWLINE_KEYVALUES_SEP_V1/
s/BW_KEYVALUES_BASIC/BWLINE_KEYS_V0/
s/BW_KEYVALUES_FILE/BWLINE_KEYS_V1_1/
s/BW_KEYVALUES_EXTRA_BWS/BWLINE_KEYS_V1_2/
s/BANDWIDTH_LINE_KEY_VALUES_MONITOR/BWLINE_KEYS_V1_4/
s/BW_KEYVALUES_EXTRA/BWLINE_KEYS_V1/
s/BW_KEYVALUES_INT/BWLINE_INT_KEYS/
s/BW_KEYVALUES/BWLINE_ALL_KEYS/
s/EXTRA_ARG_KEYVALUES/HEADER_KEYS_V1X/
s/STATS_KEYVALUES/HEADER_KEYS_V1_2/
s/BW_HEADER_KEYVALUES_RECENT_MEASUREMENTS_EXCLUDED/HEADER_RECENT_MEASUREMENTS_EXCLUDED_KEYS/
s/BW_HEADER_KEYVALUES_MONITOR/HEADER_KEYS_V1_4/
s/BANDWIDTH_HEADER_KEY_VALUES_INIT/HEADER_INIT_KEYS/
s/KEYVALUES_INT/HEADER_INT_KEYS/
s/UNORDERED_KEYVALUES/HEADER_UNORDERED_KEYS/
s/ALL_KEYVALUES/HEADER_ALL_KEYS/

Part of #30196

As in chutney and stem:
- Test all supported python versions
- Test all supported tor versions

Differences between chutney, stem and sbws:
- in sbws we run directly, not an script that calls tox
- we're not using chutney for integration tests (yet) and therefore we're not testing it with different networks
- we don't have shellcheck tests
- we don't support osx nor windows

Closes: #30067

when setting vote and unmeasured Keys.
It doesn't matter here because there're not operations with the
Keys and they're always converted to string in the bandwidth file,
but it less confusing as integer.

to test that the `under_min_report` KeyValue is added when the
number of eligible relays is less than the 60% of relays in the
consensus.

and run generate as part of the integration tests.
This allows to later check that the testnet genearted files
contain the expected Keys and Values with an script in #29727.

even if the minimum percent was not reach.

Closes: #29853.

Since when a destination fails, all the threads using it will also
fail that moment.
For now not checking which threads are actually using it.
Also lower the time to retry.

Closes: #29891.

measuring unique relays.
Create new module heartbeat.

Closes: #28652

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.

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.

Closes: #29589.

Part of #28565.

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

Closes: #28567

Part of #28567.

in the results file.

Part of #28567.

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

for every result that is stored.

Part of #28566.

Part of #28566.

used to run the scanner.
The test that runs the scanner was introduced by #28788.

Closes: #29299.

To be able to add them to the bandwidth file so that we can
diversify the locations and/or know how the location affects the
bandwidth results.

Change tests added in #28897 with the changes introduced in #28736.

Add methods to store consecutive destination failures and retrieve
the destinations that are still functional.
Since destinations can fail because of Tor circuits, it's not count
individual failures but consecutives one.
Also exit with error if there are no functional destinations left.
The maximum number of consecuitve failures is set to 10, but it
may need to be changed depending on the percentage of circuits and
requests that fail.

in every measurement.
This removes the need for an extra lock for every measurement
It should also not be depending on a time interval, but on the
number of failures detected.
Not counting number of failures since it would need to modify the
destination or list of at runtime. It should be done in a future
refactor.

Fixes bug #28897. Bugfix v0.3.0

and create function to set options that can fail because they are
not supported by some Tor versions at runtime.

Fixes bug 28692. Bugfix v0.4.0

The log message might not correspond to the reason.
Only the first one that fails will be logged, but not refactoring
here.
Add an integration test to check a runtime option fails.

to a function.
Replace comment by docstring.
Add an integration test to check the option is set.

Closes: #29551. Bugfix 1.0.3-dev0.

and put the result in the queue with a timeout.

Fixes bug #28866. Bugfix v0.1.0.