Allow Tagging of Trigger & Webhook Log Messages#598

Allow us to tag Trigger executed log messages so that we can set permissions on them.
Along with tagging the Webhook log messages for Successful & Failed requests.

Why?
So that we can add permissions on the log messages of who can see them within our organisation.

Usecase:
1. Log specific user information to their console when they join, to allow for more in depth logging.

• Join Logs: [steam ID] - [Username] joined with [IP address]

2. Provide responses to plugin messages from Battlemetrics that you otherwise wouldn’t be able to.

• [My Cool AntiCheat] [steam ID] has a violation level of 30%

  We can tag this already. Perfect.

• Trigger system detects: [My Cool AntiCheat] and does a few checks & actions related to it
• Trigger then actions a Log message with results of it’s findings
  • EX: [steam ID] - [Username] does not meet threshholds to action on

    These messages are UNABLE to be tagged.

3. This would allow the ability to enable the Webhook Logging results to All - Log successful and failed requests

• Who cares? Well everyone outside of the small number of people who understand what that webhook is doing and where it’s going.
• Hiding these from normal staff would be very helpful.