v1.2.0 - Expanded community configuration

In this update, various configuration options are split into several smaller options to provide more detailed customization of Barricade's behavior to match your community's needs and desires.

Changes

• Split up the "Reports feed" setting into "Reports feed", "Confirmations feed" and "Alerts feed"
  - By default, confirmations and alerts will be sent to the same channel as incoming reports
  - The confirmations feed can be removed to receive report confirmations via DMs instead
  - The alerts feed can be removed to stop receiving player alerts

• Split up the "Admin role" setting into "Admin role" and "Alerts role"
  - By default, alerts will use your admin role
  - The alerts role can be removed to not receive a push notification when an alert is received

• The config overview has been updated with the new settings
  - Run the /config view command to get an overview of all settings available

• Automatically dismiss submission URLs to avoid reports with duplicate tokens
  - Previously, generated URLs would have to be manually dismissed by the user
  - If the user reuses the same URL for multiple reports, only the first will be received
  - The message is now automatically dismissed to avoid the user accidentally reusing the same URL

• Bug fixes and other improvements
  - Made (un)ban failure reasons more descriptive
  - Added or removed various ellipses according to HCI standards
  - Updated an enrollment error message to clarify multi-platform community ownership
  - Fixed the report confirmation notification being suppressed
  - Fixed an issue with integrations that could cause the underlying connection to be silently closed
  - REST: Added a token field to /reports and /communities/me/reports endpoints