Remove jvmrunargs lookup and update changelog (fixes #2726)

Author: ramanathan1504

log4j-core-test/src/test/java/org/apache/logging/log4j/core/lookup/JvmRunArgsIntegrationTest.java

@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<change>
+  <summary>Removed the jvmrunargs lookup due to lack of clear use case and potential for confusion. See issue #2726 for details.</summary>
+  <issue>2726</issue>
+  <author>ramanathan1504</author>
+  <date>2025-08-14</date>
+</change>

log4j-core-test/src/test/java/org/apache/logging/log4j/core/lookup/JvmRunArgsLookupTest.java

@@ -1052,41 +1052,3 @@ You can check out the following files for examples:
 
 * {project-github-url}/log4j-core/src/main/java/org/apache/logging/log4j/core/lookup/LowerLookup.java[`LowerLookup.java`] – <<LowerLookup>> lower-cases its input
 * {project-github-url}/log4j-core/src/main/java/org/apache/logging/log4j/core/lookup/EventLookup.java[`EventLookup.java`] – <<EventLookup>> extracts specified fields from the effective `LogEvent` in the context
-
-[[JVMRunArgsLookup]]
-== JVM Runtime Arguments Lookup
-
-The `jvmrunargs` lookup allows retrieval of the JVM runtime arguments
-passed to the Java process at startup.
-
-=== Usage
-
-Use the `${jvmrunargs:<index>}` syntax, where `<index>` is the zero-based
-position of the JVM argument to retrieve.
-
-For example:
-
-[source,xml]
-----
-<Appenders>
-    <Console name="Console" target="SYSTEM_OUT">
-        <PatternLayout pattern="JVM Arg[0]: ${jvmrunargs:0} %m%n" />
-    </Console>
-</Appenders>
-----
-
-If the specified index is out of range, the lookup returns `null`.
-
-=== Example Output
-
-Given the following JVM startup arguments:
-
-The lookup expressions would produce:
-
-- `${jvmrunargs:0}` → `-DexampleArg=value`
-- `${jvmrunargs:1}` → `-Xmx512m`
-
-=== Notes
-
-* This lookup was fixed in version 2.25.0.
-* If no JVM arguments are available, all lookups will return `null`.