xF2 Add-on Warning Improvements by Xon 2.9.5

• Fix ensure the 'pending expiry' flag is kept consistent, reducing unexpected queries
• Fix deleting warning categories
• Add basic flood-check to prevent issuing duplicate warnings against the one bit of content
• Add feature 'censor warning title' for users without the new 'Bypass warning title censor' permission, supports regex removal of chunks of warning titles
• New replaceable 'warning_title_uncensored' for conversations & notification posts. 'warning_title' is censored.
• When a member is viewing a member viewing a warning, do not show "Performing moderation duties" and instead showing "viewing members".
  Moderators viewing a member viewing a warning now show the warning that is being viewed.
  Members viewing a moderator viewing a warning still show "Performing moderation duties".

• Remove redundant SQL query on user profile when a user's warning actions can't actually be viewed

• Requires php 7.0+
• Now depends on Standard Library by Xon
• Confirmed XF2.2+ support

• Fix missing phrase when blocking deleting the last warning category
• Rework warning category deleting to ensure cleanup happens atomically
• Fix handling warnings being removed when the linked category/warning action have been deleted
• Ensure orphaned warning actions are cleaned up on upgrade
• Disable change logging of sv_pending_warning_expiry state flag

• Patch XF's usage of points phrase in a user's list of warnings to use svWarningPoints phrase

• Only show warnings the viewing user can see.
  • Support for User Essentials v2.7.0 "[UserEss] Warn posts in own thread" permission.

• Ensure warnings & notifications are transactional
• Add content action variable to message replacements (thanks @TickTackk)
• Support anonymized warning conversations

• Remove XF2.0 support, require XF2.1+
• Fix case where the alert/push notification for a warning is not correctly anonymized

• Fix error when Report Improvements is not installed/enabled and notices for warnings/warning actions are created
• Use phrase groups instead of individual phrases when creating threads/posts for Warnings and Warning Actions

• Ensure thread notifications do not occur inside the transaction when issuing a warning that causes warning action notifications