Right now, AbuseFilterViewEdit not only shows the interface for editing filters, but also handles the process of validating the input and saving a filter. As a result, it is impossible to use PHPUnit to create filters programmatically, to be used for unit testing later on.
Essentially, AbuseFilter is not using a MVC (or similar) model, and we should move towards it. As a first step, let's abstract out the parts of `includes/Views/AbuseFilterViewEdit.php` that deal with validating user input (on the edit filter form) and saving it to the database, into a separate method under `includes/AbuseFilter.php` perhaps a static method called `AbuseFilter::saveFilter()` (or even better, a public static method `AbuseFilter::saveFilter()` that validates input and a private static method `AbuseFilter::doSaveFilter()` that actually writes to the database).