Override items from super classes when generating config documentation

[radcortez]

• Fixes Config docs generation error when inheritance is used #41892

The fix could be better by using a Map instead of a dumb List search, but we don't want to change the code too much due to some significant refactorings coming.

[quarkus-bot]

/cc @brunobat (opentelemetry)

[gsmet]

I added two small non-blocking comments. Feel free to either edit the commit or merge it as is :).

[gsmet]

I know it's not mandatory but I would say it's a good practice to keep the annotation, given the annotation processor is annotation driven.
They get discovered anyway when analyzing the config but this makes it discovered right away by the AP.

[radcortez]

When this annotation is present in a super class relative to the mapping class, we do generate duplicate entries of the configuration, because we handle @ConfigGroup as a nested element and not as an inherited element.

We could also fix that in the code, but I think that super classes are not config groups, so it is a bit misleading to add that annotation.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 4a88da1.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.