Avoid using -proc:full when compiling ShardingSphere with OpenJDK23

[linghengqian]

For #32927.

Changes proposed in this pull request:

• Avoid using -proc:full when compiling ShardingSphere with OpenJDK23. This is mostly to align the behavior of Support building and using ElasticJob with JDK23 shardingsphere-elasticjob#2454. Changing the default value of -proc on JDK23 is probably not a good idea.
• Since org.apache.shardingsphere.sqlfederation.optimizer.planner.rule.transformation.PushProjectIntoScanRule is generating org.apache.shardingsphere.sqlfederation.optimizer.planner.rule.transformation.ImmutablePushProjectIntoScanRule through org.immutables.processor.ProxyProcessor, the scope of annotationProcessorPaths is quite scattered. See Immutables can't be used from Java 9 modules immutables/immutables#713 .
• Bump Lombok to 1.18.36 for further support of JDK23. See https://projectlombok.org/changelog and [FEATURE] JDK 23 compatibility projectlombok/lombok#3722 .
• It is hard to explain why ShardingSphere uses org.immutables:value:2.9.3. Calcite actually always uses org.immutables:value:2.8.8.🤔
• JDK 23 and JDK 23.0.1 have a lot of bugs so far, and they continue to break unit tests related to GraalVM Tracing Agent. See [GR-59849] jdk.graal.compiler.util.json.JsonParserException thrown when using GraalVM Tracing Agent oracle/graal#9929 .
• Feel free to test the current PR.

sdk install java 23-open
sdk use java 23-open
./mvnw clean install -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e
./mvnw clean package -f examples/pom.xml -T1C

---

Before committing this PR, I'm sure that I have checked the following options:

• My code follows the code of conduct of this project.
• I have self-reviewed the commit code.
• I have (or in comment I request) added corresponding labels for the pull request.
• I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
• I have made corresponding changes to the documentation.
• I have added corresponding unit tests for my changes.
• I have updated the Release Notes of the current development version. For more details, see Update Release Note