Pending deletion message is different between groups and projects

Problem

When deleting a group or project, it is necessary to delete the group or project in question twice to ensure it is completely deleted. This is because deletion protection is enabled by default for all groups and projects.

After the first deletion step, a message is shown to the user that:

• Projects: Deletion pending. This project will be deleted on XXXX-XX-XX. Repository and other project resources are read-only.
• Groups: This group, its subgroups and projects has been scheduled for removal on XXXX-XX-XX.

Projects (old)	Projects (recently updated by paper cuts)	Groups

Let's align the experience between groups and projects.

Proposal

Have pending deletion message be a full-width, non-dismissible warning alert that appears on all pages of the assets that are pending deletion.

Projects	Groups

Notes:

• This change has mostly already been made on projects by the paper cuts team. The only thing that needs updating in the project messaging is the text.
• Group messaging needs updating to match the project experience, as shown (replacing the info alert with a full-width, non-dismissible warning alert, adding the pending deletion badge, and removing the additional orange text from the overview page). Note that, to match current behaviors in projects, the alert should display on all pages of the group that's pending deletion (example). It should also display on all assets that are pending deletion within the group, including sub-groups and projects. This is different than current behaviors; currently the alert only appears on sub-groups. The message on sub-groups and projects is slight different: The parent group of this project/group is pending deletion, so this project/group will also be deleted on YYYY-MM-DD. Example. Note that these sub-groups and projects would also need the Pending deletion badge on their overview pages, as well.
• There is one difference in behavior that will remain between groups and projects after these changes are made. Assets within projects are read-only when the project has been marked for deletion. This is not true for groups as additional changes would need to be made to allow for the read-only state. More information.
• As part of this work, we'll need to verify that the change populates properly in organizations, as well, to not introduce any additional inconsistencies.

Note that this issue ideally should be implemented in tandem with Update "removal" language to "deletion" for groups (#454586 - closed) to remove the additional remove/delete inconsistencies between groups and projects.

Figma