Fixes #25184.

Changes proposed in this pull request:

• Add the shardingsphere-infra-expr module for put all groovy related logics here.
• Add the shardingsphere-infra-expr-spi sub-module, which contains the JVMInlineExpressionParser interface that can be used by each sub-module.
• Add the shardingsphere-infra-expr-core sub-module.
• Add the shardingsphere-infra-expr-hotsopt and shardingsphere-infra-expr-espresso sub-modules.
• Note:
  • Unfortunately, I believe it is not possible to convert Copy Jar's Maven Goal into Byte Buddy related APIs for use, as this seems to be different from the requirements of Espresso. Moreover, at present, the Maven Profile of generateStandardMetadata has to intentionally skip unit tests related to Byte Buddy. We need to wait for more processing at Offer API to interact with Assisted Configuration agent oracle/graal#3969 (comment) .
  • In order to find the actual location of the Jar, it seems that the Maven Goal of Copy Jar must be placed in the Espreso module instead of the Core module.
  • The EspressoInlineExpressionParser was made into an Impl of SPI, which resulted in it having to delay the initialization of the Truffle Context class instance. I separated two commits to show what happened. When attempting to initialize this class, the target device must have a GraalVM instance with the espresso component installed. Reference resources https://github.com/apache/shardingsphere/actions/runs/4908381324/jobs/8764116118?pr=25509 .

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.