v11 warnings system re-working preview

The cns_warnings addon for v11 has been re-worked and massively improved recently. Here is a little preview into the improvements:

* You have options for deleting recent content submitted by the member (including posts in forum topics).
* You have options for reversing recent point transactions (in v11, the points system also got a major upgrade and now operates like a bank ledger; staff can reverse point transactions such as in the case of spam or abuse)



* All punitive actions are now hooks under hooks/systems/cns_warnings. This allows vast expansion of the warnings system. For example, you can design addons which have their own punitive action hooks (e.g. you can issue punishments specific for that addon). Here is an example with the upcoming Karma non-bundled addon I'm developing for v11:



* A new option exists on the warnings form: "Include punitive actions in message". This will auto-generate a list of punitive actions that were taken against the member in its own section in the Private Topic sent to the member. This is very useful when using save / load explanations. Previously, you had to write out punitive actions yourself in the message / edit a saved explanation/message for every warning. Now, you can write your own messages to save/load which do not include punitive actions. And you can simply tick "Include punitive actions in message" (since the auto-generated punitive actions are not included when you save a reason / message). You don't have to edit saved messages anymore for the specific actions you are taking.



* A vastly improved warnings history interface for specific warnings. It now includes the action log trail so you can see actions taken by you or other staff for this specific warning (such as when a staff member reverses a punitive action). You can see in detail every punitive action that was taken. And for actions which support undoing, an "undo" link will be visible allowing you to quickly undo / reverse specific actions (such as for appeals).



Behind the scenes, the database schema was changed. Previously, punitive actions were stored as columns in f_warnings. Now, there is a new table, f_warnings_punitive, which stores a row for each punitive action taken mapped to its f_warnings ID (and also references the name of the cns_warnings hook which issued the action).