Fix: do not leak ThreadContext into the system

this is fairly recent - since 7.4 (added in elasticGH-11075)

there's a risk plugins would assume ThreadContext to
exist or collide the 'global' constant - usually best
to import where the Java class actually gets used ...

Author: kares

logstash-core/lib/logstash/java_pipeline.rb

@@ -8,10 +8,11 @@
 require "logstash/compiler"
 require "logstash/config/lir_serializer"
 
-java_import org.apache.logging.log4j.ThreadContext
-
 module LogStash; class JavaPipeline < JavaBasePipeline
   include LogStash::Util::Loggable
+
+  java_import org.apache.logging.log4j.ThreadContext
+
   attr_reader \
     :worker_threads,
     :events_consumed,

logstash-core/lib/logstash/pipeline.rb

@@ -12,11 +12,11 @@
 require "logstash/filter_delegator"
 require "logstash/compiler"
 
-java_import org.apache.logging.log4j.ThreadContext
-
 module LogStash; class BasePipeline < AbstractPipeline
   include LogStash::Util::Loggable
 
+  java_import org.apache.logging.log4j.ThreadContext
+
   attr_reader :inputs, :filters, :outputs
 
   def initialize(pipeline_config, namespaced_metric = nil, agent = nil)