Ubuntu 21.10 (Impish) has reached end-of-life and the image could no
longer be built.

contrib: add distrotest for rocky8

See merge request !116

contrib/docker: utility scripts for image updates

See merge request !115

respdiff: downgrade bind to previous working version

See merge request !114

contrib: update resolvers

See merge request !113

orchestrator: fix progress report

See merge request !112

For some reason, the code reading answers was using imap() function to
read them _in order_ they were sent. This could cause answer buildup
in an internal multiprocessing queue, and eventually the program logged
multiple 'Received xxx answers' lines at once, which made the status
reporting useless.

It was like that since d422292d, and
this commit claims it reduced storage requirements by factor 25.
The problem is that the commit did three changes at once:
- it moved txn.put() into central place in the main thread
- it coalesced all writes into one huge transactoin
- it changed imap_unordered() to imap() call

In my tests today, centralized txn.put() in the main thread in
combination with one huge transaction and imap_unordered() increases
storage size by 5 %, and that does not seem worth incorrect status
reporting.

Tested with LMDB version 0.9.29.

contrib/job_manager: add ubuntu2110, fedora35, delete older

See merge request !111

ci: update to knot 3.1 and debian 11

See merge request !110

use respdiff-rs version of msgdiff

See merge request !109

contrib/job_manager: add distrotests for debian11

See merge request !108

contib: update fedora, ubuntu releases

See merge request !107

diffsum: display msgid for queries

See merge request !106

Knowing the specific message ID can be useful for debugging purposes.
The displayed value is the actually message ID contained in the query,
not the respdiff's internal query ID (QID) used for identification in
LMDB.

ci: updates

See merge request !104

This was used only for a sigle test with malformed queries. However, it
wasn't maintained and no longer running in CI. Furthermore, updating
deckard would require extra privileges and additional changes related to
removal of socket wrapper. The single test doesn't seem to be worth the
effort.

contrib/docker: update dnsperf

See merge request !103

bind: update Dockerfile

See merge request !102

contrib/job_manager: bump unbound to version 1.13.0

See merge request !101

remove rebinding module

See merge request !100