CONFIG_DEFAULT_SECURITY_APPARMOR=n not working for Nitrogen8MM unless CONFIG_SECURITY_APPARMOR=n

[acostach]

The default security is still set to apparmor unless apparmor is completely disabled. The OS sets CONFIG_DEFAULT_SECURITY_APPARMOR=n but this is not the final result during a build, we need to look into why this happens.

Internal thread https://balena.zulipchat.com/#narrow/stream/345889-balena-io.2Fos/topic/multicontainer.20sample.20app.20fails.20to.20start.20in.20v2.2E113.2E35/near/348391746

Connects to balena-os/meta-balena#3099

[acostach]

The generic-x86-64 is on kirkstone, has kernel 5.15 and also has DEFAULT_SECURITY_APPARMOR=y in the defconfig but it ends up disabled in the final config even if meta-balena doesn't set it to n.

For the Nitrogen this is still not disabled, neither with kernel 5.15 (not yet published by BSP) and kirkstone.
Needs further investigation