Disable -jpms-multi-release BND option

Due to limitations of BND 6.x and the build process of our multi-release
JARs, this option was never effective.

We could reenable it in multi-release JARs that have a difference in
package and module dependencies between Java versions.

Author: ppkarwasz

pom.xml

@@ -1026,9 +1026,6 @@ import org.apache.commons.codec.digest.*;
             # Allow each project to override the `Multi-Release` header:
             Multi-Release: $[bnd-multi-release]
 
-            # Add manifests and modules for each multi-release version:
-            -jpms-multi-release: $[bnd-multi-release]
-
             # Adds certain `Implementation-*` and `Specification-*` entries to the generated `MANIFEST.MF`.
             # Using these properties is known to be a bad practice: https://github.com/apache/logging-log4j2/issues/1923#issuecomment-1786818254
             # Users should use `META-INF/maven/<groupId>/<artifactId>/pom.properties` instead.

src/changelog/.10.x.x/disable_jpms_multi_release.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<entry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+       xmlns="http://logging.apache.org/log4j/changelog"
+       xsi:schemaLocation="http://logging.apache.org/log4j/changelog https://logging.apache.org/log4j/changelog-0.1.3.xsd"
+       type="changed">
+  <issue id="93" link="https://github.com/apache/logging-parent/pull/93"/>
+  <description format="asciidoc">Disable https://bnd.bndtools.org/instructions/jpms-multi-release.html[`-jpms-multi-release`] BND option.</description>
+</entry>