Description

Signed/unsigned containers are not marked as such by the UI, even when the 'container signing' feature-flag is enabled. This is because the UI is relying on the `display_signatures` flag, which is only set when collection signing is enabled.

This affects on-prem.

Steps to Reproduce

Install AAP with a container signing service configured, but not a collection signing service.

Always reproduceable.

Navigate to a container to sign it.

Actual Behavior

 There is no unsigned or signed badge on any container, regardless of signed status.

Expected Behavior

There should be an accurate badge indicating the signing status of each container.