Irrd

* Startup could fail (937) when using the user/group settings. This happened because of
an incorrect log file access check.
* Deletes are now non-strict (912) which means legacy objects that are currently
not valid can be deleted without fixing the object first.
* The irr_rpsl_submit command could log an RPSL password for certain failures (bb8cb94cc3d64564788dca96d29efaf74c25544c)

* Password hashers configured as legacy were incorrectly not
available for authentication.
* The password validation did not gracefully handle maintainers
that had no currently supported authentication methods.

and 4.4.1 where set member queries were incorrectly case sensitive (868).

where instances using readonly_standby would fail to start (861).
It also fixes some minor display issues in the web interface.

Highlights of new features:

* A new web interface offering internal authentication for
improved flexibility, security and user-friendliness.
* A new method for running standby instances, mainly for
authoritative databases.
* Protection of previously used `mntner`, `person` and `role`
names, and an option to delete such objects with override.
* Source aliases that can be used in queries.
* Preloading of set members, improving performance for all
queries that include `as-set` and `route-set` resolving.

First beta of 4.4.0: https://irrd.readthedocs.io/en/latest/releases/4.4.0/