Podman: review usage of privileged and cap_add flags

[mfarina1]

Review usage of privileged and cap_add flags for nm-manager containers. These flags sometimes behave differently in Podman, and it is best practice not to use them if not actually needed.

[DavidEdell]

The privileged and cap_add flags are currently used only by the ion-* containers. The usage of these flags is not causing any issues under podman for common use cases. It is possible that these flags are not behaving under podman the same as they do under Docker, indicating that their usage may not be required in the first place.

[mfarina1]

The current compose configs work for Brian in a production-like deployment with selinux under systemd.

According to David, the only thing that doesn't work (only partly related to this ticket), is that if you don't define the SELinux tags/policies on a system that supports it, particularly with podman, it will fail to start.

Otherwise this issue can be closed