Revamp process for requesting mainsite submission removals

[VinnyVideo]

Currently, the process for requesting mainsite submission removals isn't terrible, but it is a bit clunky.

As a submitter, if you want a submission removed, you click the "Request Removal" button from the submission view. Once a mainsite QC staffer approves your removal request, the submission will no longer be accessible on the site. This process requires a manual approval to make sure your request is legit, just in case a malicious user hacked your account or something.

Once the submission is removed, the system automatically deletes the database entry, making it very hard to restore your submission if you change your mind. Yet the file itself isn't always removed, resulting in ghost files cluttering up the system.

Here's an alternative workflow to consider.

1. User clicks "Remove Submission" button.
2. Submission is marked as "Removed by user" in database, making it no longer visible when you click on the submission page or run a search.
3. Site staff receives a notification (no action required) that a user removed a submission.
4. Submission's database entry and file are purged after a certain amount of time (maybe a year?)

This delivers quicker results for submitters, less work for site staff, and improved ability to restore a submission if someone changes their mind.

A similar process could potentially be used for declined submissions - site staff could view declined submissions for a certain amount of time.