Update library to serve building GraalVM Native Image

[linghengqian]

For #21347.

Changes proposed in this pull request:

• Introduce junit-vintage-engine to support unit testing inside GraalVM Native Image. Reference Support JUnit 4 via the VintageTestEngine graalvm/native-build-tools#53 .
• Update HikariCP to the highest possible version to better match the graalvm reachability metadata at https://github.com/oracle/graalvm-reachability-metadata/tree/master/metadata/com.zaxxer/HikariCP/5.0.1 .
• Update netty to 4.1.84 to get the new automatically generate native-image conditional metadata for ChannelHandler implementations. See Automatically generate native-image conditional metadata for ChannelHandler implementations. netty/netty#12794 .
• Update logback to match graalvm reachability metadata at https://github.com/oracle/graalvm-reachability-metadata/tree/master/metadata/ch.qos.logback/logback-classic/1.2.11 .
• Update maven-surefire-plugin to milestone version to automatically handle use of org.junit.platform:junit-platform-launcher. Reference https://graalvm.github.io/native-build-tools/latest/maven-plugin.html#testing-support-version-compatibility .
• Update mockito to be in sync with the latest Junit Platform requirements as much as possible.
• Update most of the dependencies to get https://github.com/oracle/graalvm-reachability-metadata support faster in the future. The exception is jetcd, if we had to exclude Guava, that would break a bunch of weird behavior of io.etcd:jetcd-grpc:0.7.3. I have some ideas at Hope to update CHANGELOG etcd-io/jetcd#1091 but haven't started working on that issue yet. atomikos has some changes from 5.0.8 to 5.0.9, but I can't see anything in its git commit log....I will rollback this part of the process.
• 
• Handle most deprecated methods.
• Update LICENSE.

---

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 : mvn clean install -B -T2C -DskipTests -Dmaven.javadoc.skip=true -e.
• I have made corresponding changes to the documentation.
• I have added corresponding unit tests for my changes.

[codecov-commenter]

Codecov Report

Merging #21552 (0275ffd) into master (22313c9) will decrease coverage by 0.21%.
The diff coverage is 8.33%.

❗ Current head 0275ffd differs from pull request most recent head d51be2b. Consider uploading reports for the commit d51be2b to get more accurate results

@@             Coverage Diff              @@
##             master   #21552      +/-   ##
============================================
- Coverage     61.21%   60.99%   -0.22%     
- Complexity     2509     2510       +1     
============================================
  Files          4109     4115       +6     
  Lines         57124    57346     +222     
  Branches       7560     7592      +32     
============================================
+ Hits          34967    34981      +14     
- Misses        19222    19430     +208     
  Partials       2935     2935              

Impacted Files	Coverage Δ
...etadata/data/ShardingStatisticsTableCollector.java	0.00% <0.00%> (ø)
...uilder/dialect/MySQLShardingSphereDataBuilder.java	0.00% <0.00%> (ø)
...r/dialect/PostgreSQLShardingSphereDataBuilder.java	0.00% <0.00%> (ø)
...nfra/yaml/data/pojo/YamlShardingSphereRowData.java	0.00% <0.00%> (ø)
...ra/yaml/data/pojo/YamlShardingSphereTableData.java	0.00% <0.00%> (ø)
...ta/swapper/YamlShardingSphereTableDataSwapper.java	0.00% <0.00%> (ø)
...line/core/api/impl/AbstractPipelineJobAPIImpl.java	0.00% <ø> (ø)
...ine/core/api/impl/GovernanceRepositoryAPIImpl.java	0.00% <0.00%> (ø)
...e/api/impl/InventoryIncrementalJobItemAPIImpl.java	0.00% <0.00%> (ø)
...ore/api/impl/PipelineDataSourcePersistService.java	0.00% <0.00%> (ø)
... and 24 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[linghengqian]

• Some magical GHA issues happened in this PR. Atomikos has added a new keepaliveTime property from 5.0.8 to 5.0.9. I switch atomikos.version in different commits of the PR. If GHA keeps the cache, I can easily see this problem... But the process of changing atomikos.version happens in the child pom.xml for the module, not sure what to do.

• I'll submit a new PR on the new branch shortly.

• 

[linghengqian]

New PR at #21571 .