Missing fields in a data-form response are now interpreted as an empty value

Merge branch 'v7'

Fix a crash when botan policy does not allow any available ciphersuite

Fix the test_suite by using catch’s single_include directory

Only use the ID to order archives

fix #3343

Revert "Use a different Date data type"

This reverts commit 857c7d3972a03cbeebf730d99b924d3710dee6a0.

Revert "Use the Date to find a next page in RSM, not the id"

This reverts commit 5ef7ba08028065b03d51d1dc70bb35aeb41ae19d.

Add a note about multiple admins in the ChangeLog

Add a note about multiple admins in the manpage

Use Config::is_in_list() to allow for multiple admins

Add a Config::is_in_list() method

Use jid.bare() instead of manual concatenation

Use the Date to find a next page in RSM, not the id

This way, it works, whatever the order of insertion in the database was.

fix #3343

one log_debug -> log_error, also some trivial indent

Remove two unused (julianday) functions

Refactor that fixes a compilation issue in Release mode

Some template specialization were not found, because they were not declared
at the point they were used.

We moved things around, things are less inter-dependant, and also now it
works.

Fix a build warning when compiling without postgres or sqlite

Use a different Date data type

PLEASE backup your database before testing this commit, and report any
migration issue.

In postgresql, we use timestamp with timezone.
In sqlite3 we use REAL (the date is expressed as julianday)

This requires a migration of the muclogline_ table:
In postgresql it’s pretty simple, we convert all the integer into timestamps

With sqlite3, we actually rename the table, create the new one with the
correct type, then copy everything to the new table, with a conversion
function for the Date_ column, and then we delete the old table.

fix #3343

Send the stanza-id for messages received by other users

fix #3347

Fix the e2e test broken by previous commit