Show why a project is blocked in the admin panel

[Erin007]

LP-352

We'd like to give admins more insight into why a project is blocked from sharing. There are four reason why a project could be blocked:
1.) Sharing is disabled for the owner
2.) There is potentially profane or private information in the project text, caught by WebPurify
3.) There is a potentially inappropriate image associate with the project, caught by image moderation
4.) The project has been manually reported for abuse enough that the abuse threshold is reached

In this change, I expose which (if any) of these criteria have been met in the admin panel for projects.

Examples

Safe to share:

Sharing is disabled:

Manual abuse reports:

Both sharing is disabled and manual abuse reports:

Upcoming work:

• displaying which term was flagged by the profanity/privacy text filter
• only showing enable/disable content moderation buttons when applicable based on project type

[davidsbailey]

tangential question, but if a featured project has an abusive image added to it the new starting score of -50, that won't be enough to "automatically" block the project, right? I think this is probably ok... because we choose who to feature, and the abusers are relatively unlikely to be selected... just confirming I understand the implications here.

[Erin007]

Yes, you are correct. If an abusive image is added to a project while it is featured, then the increment on the abuse score via the image moderation service would not be enough to block the project.

[maddiedierker]

yay, this is super useful!