Part of task-25002.

Relays include the $ in fingerprints that they report in their family
line. We remove that $ when computing effective and extended families
and add it back later when writing details documents. With this change
we're taking out that last step.

Implements #22261.

Add a "recommended_version" parameter to return only relays and
bridges running a Tor software version that is recommended or not
recommended by the directory authorities.

Implements #23544.

Add a "recommended_version" field to bridge details documents based on
whether the directory authorities recommend the bridge's version.

Implements #21827.

Extend the "version" parameter to also return bridges with the given
version or version prefix.

Implements #23962.

Add a "version" field to relay details documents with the Tor software
version listed in the consensus and similarly to bridge details
documents with the Tor software version found in the server
descriptor.

Implements #22488.

We said we'd announce new major versions 1 month in advance. Today
we're going to put out a release to include this date for the first
time. Re-scheduling next major version for in 1 month from today.

Implements #21637.

Implements #16553.

Optimistically schedule the next major version for end of this month
for removing $ from family fingerprints. That's a rather small
backward-incompatible change, so it should be fine to reduce the
notification period to a bit under four weeks. But just in case we
want more time we can always push that back by a week or two. At least
we're now saying that there will be a major version update soon.

The testCountryDeDe typically requires around 80 to 100ms to complete,
which makes our test timeout of 100ms somewhat optimistic. The reason
is that it's the first test method that is run in this test class, and
it takes some time to initialize the test environment. This is just a
hotfix, but it's also not really a serious problem, so maybe it'll
just do.

With this patch, the "search" parameter does not only accept unquoted
qualified search terms like `search=contact:John Doe` where "John"
would be looked up in the contact line and "Doe" in the nickname or
base64-encoded fingerprint. It also accepts quoted qualified search
terms like `search=contact:"John Doe"` where "John Doe" would be
looked up in the contact line. It further accepts escaped double
quotes (\") within quoted qualified search terms.

Implements #21366.

There's a relay running an alternate Tor version that produces
descriptors without "uptime" line, and the directory authorities don't
include a "v" line for that relay, likely because its platform string
does not include the magic word "Tor".

Fixes #24012.

Implements task-23778.

When we set this field in the update process, we only looked whether
the bridge is contained in the last known bridge network status. We
also need to check whether it has the "Running" flag assigned there.

This is different from relays, because the consensus only lists relays
with the "Running" flag since a couple of years, whereas the bridge
network status lists all known bridges.

Fixes #23467. Spotted by nusenu.

Implements #23548.

Also, added error logging for indexing process.