in RelayList:
- Rename consensus_timestamps to recent_consensus
- Rename recent_consensus_count to recent_consensus when there is
  no counting
- Use the timestamps class to manage/count consensuses
- Remove method not needed anymore

to be able to serialize/deserailize datetime in the state file.

Since state uses json and json will raise an error when it can't
decode/encode some datatype.

Otherwise, if other instance of state set a key, it's lost by the
current instance.

Bugfix v0.7.0.

Test that two different instances of state don't overwrite each other.
This test don't past in this commit, will pass in the next bugfix.

Bugfix v0.7.0, which claimed 100% test coverage on state.

Part of #30196

Part of #30196

Part of #30196.

Part of #30196.

by version.

Part of #30196.

- 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.

Replace HEADER_INIT_KEYS constant KeyValues with other constants
created in the previous commit.

Part of #30196.

- Add new KeyValues constants
- Remove HEADER_KEYS_V1X constant, only used once
- Replace HEADER_UNORDERED_KEYS with the new constants

Part of #30196.

to build the list of all keys from it and ensure no key is missing.

After the automatic constants renaming, fix the flake8 errors by
reformatting automatically with `black`, only the lines that had
errors.

Part of #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

Update relay status before updating the consensus timestamps
Timestamps that are not old yet were getting removed because the
document.valid_after timestamp was still the one from the previous
consensus.

Closes #33570.

This test does not pass in this commit, but in the next bugfix.

since the logic is the same and the there were two bugfixes on the
same logic.

by default days is passed to timedelta, what was making the oldest
date be thousands of days in the past.

Bugfix 1.1.0.

Tests don't pass in this commit, they're fixed in the next commits.

to be able to unit test all the code that needs a controller.

Tests don't pass in this commit, it's fixed in the next commits.

by default days is passed to timedelta, what was making the oldest
date be thousands of days in the past.

Old timestamps are minor than the older date, not major.

The tests don't pass in this commit, it's fixed in the next ones.

Instead of having a hardcoded version, calculate the version at build
time making use of `git describe --tags --dirty --always`.

This way, even if the program is not running from inside a git
repository it still can know which was the git revision from the
source it was installed from.
If the program is launched from a path that is a git repository, it
does not gives the git revision of that other repository.

If's also able to get the version when installed from a tarball.
It does not add the git revision when it's being install from a git
tag.

`versioneer` external program is only needed the first time, because
it copies itself into the repository. So it does not add an external
dependency.

There're no changes needed to the `--version` cli argument nor to the
code that generates the bandwidth file, since they both use the
variable `__version__`.

The version previous to this commit was `1.1.1-dev0`, after
this commit, it becomes `1.1.0+xx.gyyyyyyyy`, ie. xx commits after
`1.1.0` plus the git short hash (yyyyyyyy).

Closes: #30899.