fix: performance issues due to missing mc packet logging filter (#1860)

### Motivation
Our logback instance replaces log4j implementations and thus also
filters that might be defined in log4j configs.

### Modification
Copied the mc packet filter to our logback config to ensure proper
filtering of network packets.

### Result
Performance issues due to massive logging resolved

Author: 0utplay

wrapper-jvm/impl/src/main/resources/logback.xml

@@ -16,6 +16,7 @@
 
 <configuration>
   <import class="ch.qos.logback.core.ConsoleAppender"/>
+  <import class="ch.qos.logback.classic.turbo.MarkerFilter"/>
   <import class="ch.qos.logback.classic.filter.LevelFilter"/>
   <import class="ch.qos.logback.classic.filter.ThresholdFilter"/>
   <import class="ch.qos.logback.core.rolling.RollingFileAppender"/>
@@ -33,6 +34,13 @@
   <!-- allow configuring log levels using properties file -->
   <propertiesConfigurator optional="true" file="${cloudnet.log.properties.file}"/>
 
+  <!-- discards mc related packets with NETWORK_PACKETS marker -->
+  <turboFilter class="MarkerFilter">
+    <Marker>${cloudnet.wrapper.log.packet-filter.marker:-NETWORK_PACKETS}</Marker>
+    <OnMatch>${cloudnet.wrapper.log.packet-filter.on-match:-DENY}</OnMatch>
+    <OnMismatch>NEUTRAL</OnMismatch>
+  </turboFilter>
+
   <property name="LOG_PATTERN" value="[%d{dd.MM HH:mm:ss.SSS}] %-5level: %msg%n"/>
   <appender name="Rolling" class="RollingFileAppender">
     <file>${cloudnet.log.path}/latest.log</file>