In containers securityfs is typically not mounted. Our lsm-bpf code so far detected this situation and claimed the kernel was lacking lsm-bpf support. Which isn't quite true though, it might very well support it. This made boots of systemd in systemd-nspawn a bit ugly, because of the misleading log message at boot. Let's improve things, and make clearer what is going on.