Ensure the archive setting is rendered even when ancestor is archived

What does this MR do and why?

Adds a test to ensure that the archive settings for groups and projects is always rendered even if they already belong to an archived group.

This section is still useful as it provides context to the user why the entity cannot be archived.

Why?

In the first version of Prevent archive/unarchive action on groups/proj... (!210188), we had a change that completely removed the section when the subject cannot be archived -- unintentionally drifting from the UX design.

This smoke test ensures we don't accidentally make the same change in the future.

References

Related to #576369

Screenshots or screen recordings

No visual change

How to set up and validate locally

No functional change

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.