Follow-up from "Geo - Does not raise error 500 on Geo projects list page for orphaned entries"

The following discussion from !7565 (merged) should be addressed:

• @stanhu started a discussion: (+3 comments)

  I think it might be ambiguous to an admin what this means:

  1. Does the project no longer exist on the secondary?
  2. Does the project no longer exist on the primary?
  3. What does the remove button actually do? (Admins might think it destroys a project and be hesitant to delete it)

  Maybe we need some extra guidance here and say something like, "Project X no longer exists on the primary." We might need to point to extra detail, something to the effect of, "The tracking entry references a project that has been removed from the database. It should be safe to delete this entry, as this will not delete any projects on disk".