#27 Continues startup with illegal AM configuration

[Cato Olsen]

Moria2 continues a fresh (re-)start even when the
Authorization Manager configuration should cause a
critical failure.

Notably, when setting illegal security levels (3) for any
attribute, the log error message is "using old database",
when no such database can exist. This results in a
critical internal error once the service in question tries to
use Moria2.

Proper behaviour should be to abort the startup
procedure with a critical error.