Protected containers: Show protection details in container detail page

In previous issues the possibility was added to protected containers from push and delete, e.g. #427546, #406797, etc.

Given this new possibility, we need to make sure that users are able to easily identify protected containers in the different pages related to the container registry. This avoids confusion and unnecessary overhead. This issue discusses and aligns the design concept and other implementation details.

A similar issue was discussed and implemented for the feature "Protected package", see #437928 (closed) . This issue intends to implement the same functionality and apply the same learnings.

This issue belongs to the EPIC Container Registry: Granular protection for rep... (&9825).

Proposal

For the container detail page, we propose to add the badge "protected" related to the container protection. As the label name suggests, this label should represent that the container is protected or not. We intend to apply the same changes that have been implemented in the context of the feature "Protected packages", e.g. !141134 (merged) and !146206 (merged).

The following screenshot is taken from the package registry that is the inspiration for this issue.

Implementation plan

• Implement new GraphQL field API that shows that the given container is protected or not => !156741 (merged)
• Implement badge to show protection info in container detail page, !156539 (merged)