Bump log4j2.version from 2.23.1 to 2.24.0

[dependabot]

Bumps log4j2.version from 2.23.1 to 2.24.0.
Updates org.apache.logging.log4j:log4j-core from 2.23.1 to 2.24.0

Updates org.apache.logging.log4j:log4j-slf4j-impl from 2.23.1 to 2.24.0

Updates org.apache.logging.log4j:log4j-1.2-api from 2.23.1 to 2.24.0

Updates org.apache.logging.log4j:log4j-api from 2.23.1 to 2.24.0

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[FlorianHockmann]

The release notes look unproblematic to me. They only mention that JMX is now disabled but I don't think that we're using JMX in Log4j.

[porunov]

The release notes look unproblematic to me. They only mention that JMX is now disabled but I don't think that we're using JMX in Log4j.

In CQLStoreManager we have options to enabled / disable JMXReporter for metrics, but I'm not aware about using it for logs.

janusgraph/janusgraph-cql/src/main/java/org/janusgraph/diskstorage/cql/CQLStoreManager.java

Lines 201 to 213 in 66fdcc7

	private void initializeJmxMetrics() {
	final Configuration configuration = getStorageConfig();
	if (configuration.get(METRICS_JMX_ENABLED) && configuration.get(BASIC_METRICS) && session.getMetrics().isPresent()) {
	MetricManager.INSTANCE.getRegistry().registerAll(session.getMetrics().get().getRegistry());
	}
	}
	private void clearJmxMetrics() {
	final Configuration configuration = getStorageConfig();
	if (configuration.get(METRICS_JMX_ENABLED) && configuration.get(BASIC_METRICS) && session.getMetrics().isPresent()) {
	session.getMetrics().get().getRegistry().getNames().forEach(metricName -> MetricManager.INSTANCE.getRegistry().remove(metricName));
	}
	}