chore: move the event logging to it's own tag

Without this, rsyslog will shunt any logging output from the dokku user to the event log, garbling output for future investigation.

plugins/20_events/install

@@ -38,7 +38,14 @@ fi
 
 if [[ -d "$DOKKU_RSYSLOG_FILTER_DIR" && ! -f "$DOKKU_RSYSLOG_FILTER" ]]; then
   cat >"$DOKKU_RSYSLOG_FILTER" <<EOF
-:syslogtag, contains, "dokku" $DOKKU_EVENTS_LOGFILE
+:syslogtag, contains, "dokku-event" $DOKKU_EVENTS_LOGFILE
+EOF
+  flag_rsyslog_needs_restart=y
+fi
+
+if [[ -f "$DOKKU_RSYSLOG_FILTER" ]] && ! grep -q "dokku-event" "$DOKKU_RSYSLOG_FILTER"; then
+  cat >"$DOKKU_RSYSLOG_FILTER" <<EOF
+:syslogtag, contains, "dokku-event" $DOKKU_EVENTS_LOGFILE
 EOF
   flag_rsyslog_needs_restart=y
 fi

plugins/common/functions

@@ -152,7 +152,7 @@ dokku_log_fail() {
 
 dokku_log_event() {
   declare desc="log dokku events"
-  logger -t dokku -i -- "$@"
+  logger -t dokku-event -i -- "$@"
 }
 
 dokku_log_plugn_trigger_call() {