When a project manifest is not writable, we know that the user does not have permission to edit the project and we hide this button as of #4837. In this case at least, we should change the Delete button to Remove to more accurately describe the action as not permanent.

A more questionable case is how to handle shared projects with full access (and no sticky bit), where we may want all three buttons (Delete, Remove, Edit). It is possible that we do not present the Delete button to prevent permanent deletion mistakes, so that even when the collaborator has the permission to delete the configuration directory they have to do this some other way (through the files app, eg.) where it is more clear exactly what is being deleted. If we do not do this, we will have to detect whether a collaborator has deletion privilege using the sticky bit (in preparation for #4781)

This is currently blocked until #4837 merges