Improve security-manager current implementation

The current implementation of the security-manager has few little defaults that can be quickly fixed:

• it is not compatible with containerization (see SPEC-2875)

• its recipes is spread in too much directories (see )

• its initialization should be checked (see )

• the location of the database has to be changed (see that provided a workaround)

All in one, I decided to create that ticket that summarize the work that can be quickly achieved to answer all this issues that are tightly coupled.