and measurement attempts from all the results.
Until they get properly updated.

Also change dates in tests, so that timestamps are counted correctly

Closes: #34309.

Maint 1.1 bug33871 scaling 03

See merge request tpo/network-health/sbws!9

Closes #33871.

so that it has its own page as it is too long as docstring and is
harder to write latex with the docstring syntax.

and without consensus bw from scaling.

Part of #33871, closes #33831.

since rounding already returns 1 as minimum.

instead of bw before scaling.

Tests have finally correct value.
For 1 result, only when the cap is 1, the value will be equal to the
rounded bw because the cap does not limit it.

Make tests pass because the high limit change the expected values,
but the final value still needs to be fixed.

Make test pass, though the value is not correct since it needs to be
rounded after clipping

Take either the consenus bandwidth or the descriptor bandwidth if
one of them is missing, do not scale when both are missing and
ignore descriptor average and burst when they are missing.

Scale relays without average or observed bandwidth.
Later it will be check what to do if their values are None or 0

since they are probably due a bug.

for each relay, calculate the filtered mean for all relays and
calculate the filtered ratio for each relay.

to calculate the filtered bandwidth for each relay.

Bug 33009 v6

See merge request torproject/network-health/sbws!6

When using `_relays_with_flags()` and similar methods it's possible
that tests start to hang without time freezing. See bug 33748 for more
details. We work around this by providing the necessary `freeze_time()`
calls meanwhile.

and not a list of timestamps.

Closes: #30905.

Added:
- library to check whether the KeyValues make sense
- test an example bandwidth file
- a command to check an arbitrary bandwidth file

Finally, doing something with all these KeyValues!

(Quarantine day 7th)

Test that the results, state and bandwidth file generated by running
the scanner and the generator in the test network are correct.

in ResultDump and incrementing relay's monitoring KeyValues.

monitoring KeyValues.

using timestamps class.

Additionally:

- fix: relayprioritizer: Replace call relay priority

- fix: scanner: Replace call relay measurement attempt

using timestamps class.
Also add one more result to the tests data and change the
test accordingly.

Tests wont' pass with this commit, they'll be fixed in the next commits

in RelayPrioritizer:
- Rename recent_priority_list_count to recent_priority_list when
  there is no counting
- Rename recent_priority_relay_count to recent_priority_relay
  when there is no counting
- Use the timestamps class to manage/count priority lists/relays

in RelayList:
- Rename recent_measurement_attempt_count to recent_measurement_attempt when
  there is no counting
- Use the timestamps class to manage/count measurement attempts