Try to get the liquibase 4.23.0 metadata

[antoinebhs]

What does this PR do?

I would like to help to add liquibase metadata for version 4.26.0 in reference to this opened issue: #431. I would need the updated metadata in my project.

I first tried to get the same metadata as the 4.23.0 liquibase on master branch using generate-metadata.sh in this PR. I use 17.0.9-graal and try to get the metadata by running the existing tests in LiquibaseCoreTest.java.
There are a lot of differences between what is committed on master branch and what I get when I run the script to get metadata with the agent. I added my results to metadata/org.liquibase/liquibase-core/4.23.0/reflect-config.json and same for resource.json to see that it's very different.

For other projects like metadata/org.hibernate.orm/hibernate-core/6.6.0.Final which has a generate-metadata.sh script on master, I get much closer results.
My questions are:

• how these metadata were obtained? Am I doing something wrong?
• Is there a cleaning step? Can I have some details on this step if so?

Any help would make it much easier to contribute to the metadata repo!

@msupic do you have any insight on how you obtained these metadata for liquibase please?

Code sections where the PR accesses files, network, docker or some external service

• (example link to code section)

Checklist before merging

• I have considered including reachability metadata directly in the library or the framework (see our contributing document)
• I am the original author of all content provided in the pull request, and I did not copy the content from any other source (see the tests section from our contributing document)
• For all tests where I am not the sole author, I have added a comment that proves I may publish them under the specified license (see the tests section from our contributing document)
• I have properly formatted metadata files (see our formatting guide)
• I have added thorough tests (see the tests section from our contributing document)
• I have filled all places where my pull request accesses files, network, docker, or any other external service (see the section above)