Fix lost application logs in plugin test scenarios

Capture both stdout and stderr in scenario.out by redirecting stderr
in run.sh. Previously only stdout was captured, but all 90+ scenarios
use SYSTEM_ERR in log4j2.xml. Also raise log level from WARN to INFO
for rocketmq scenarios to capture useful debug messages.

Author: wu-sheng

test/plugin/containers/jvm-container/src/main/docker/run.sh

@@ -84,7 +84,7 @@ export agent_opts="
     -Dskywalking.meter.report_interval=1
     -Xms256m -Xmx256m ${agent_opts}"
 
-bash /var/run/${SCENARIO_NAME}/${SCENARIO_START_SCRIPT} 1>${LOGS_HOME}/scenario.out &
+bash /var/run/${SCENARIO_NAME}/${SCENARIO_START_SCRIPT} >${LOGS_HOME}/scenario.out 2>&1 &
 sleep 5
 
 healthCheck ${SCENARIO_HEALTH_CHECK_URL}

test/plugin/scenarios/rocketmq-5-grpc-scenario/src/main/resources/log4j2.xml

@@ -23,7 +23,7 @@
         </Console>
     </Appenders>
     <Loggers>
-        <Root level="WARN">
+        <Root level="INFO">
             <AppenderRef ref="Console"/>
         </Root>
     </Loggers>

test/plugin/scenarios/rocketmq-scenario/src/main/resources/log4j2.xml

@@ -23,7 +23,7 @@
         </Console>
     </Appenders>
     <Loggers>
-        <Root level="WARN">
+        <Root level="INFO">
             <AppenderRef ref="Console"/>
         </Root>
     </Loggers>