fix (jmh) : Explicitly configure JMH annotation processor in binary-tree benchmark

[hadryyassine]

Context

Part of our RPMs QA process, When running the binary-tree benchmark demo for our RPM release for newer GraalVM versions , the benchmark demo fails with:
Exception in thread "main" java.lang.RuntimeException: ERROR: Unable to find the resource: /META-INF/BenchmarkList

This occurs because the JMH annotation processor isn't explicitly configured in the Maven build, leading to missing metadata generation required for JMH benchmarks to run.

Root Cause

The current pom.xml relies on implicit annotation processing, which can be unreliable across different build environments and JDK versions. While it might work in some environments where Maven picks up the processor automatically, it fails in other environments.

Solution

Added explicit configuration for the JMH annotation processor in the maven-compiler-plugin:

[olyagpl]

Maybe we don't need the duplicated org.openjdk.jmh in the dependency block.