Fix Spring Native after Spring Boot 3.3.3 and dependency updates

[antoinebhs]

• Broadcast update event in CI after native image is pushed
• Update native-build-tools to 0.10.3 (latest version)
• Fix build error on org.apache.commons.logging by excluding it in pom.xml to avoid conflicts (https://stackoverflow.com/questions/76706612/standard-commons-logging-discovery-in-action-with-spring-jcl):

Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
Error: Classes that should be initialized at run time got initialized during image building:
org.apache.commons.logging.LogFactory was unintentionally initialized at build time. To see why org.apache.commons.logging.LogFactory got initialized use --trace-class-initialization=org.apache.commons.logging.LogFactory

• Remove Elasticsearch metadata and multiple checksums in changelog_20211019T140751Z.xml fixed with Spring Boot update (and associated dependencies: liquibase, spring-data).
• Add resource-config hint for SubDirectoryCount to avoid repeated INFO in the console:

2024-09-19T13:10:28.750Z  INFO 1 --- [o-8080-exec-192] tionInformation$PropertyDescriptorSource : Couldn't read class metadata for interface org.gridsuite.directory.server.repository.DirectoryElementRepository$SubDirectoryCount. Input property calculation might fail

• Unfortunately metadata for liquibase 4.26 are not yet available https://github.com/oracle/graalvm-reachability-metadata/tree/master/metadata/org.liquibase/liquibase-core, so I added the metadata mentioned in the existing issue Add support for org.liquibase:liquibase-core:4.24.0 oracle/graalvm-reachability-metadata#431 on their side. It's a pity that this repository is not often updated...

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud