Work around config doc issues for LGTM

[gsmet]

There are several issues:

• first, the config doc processor is part of the extension processor for now, so you need to run it to analyze the config.
• second we need to mark at least one class with @ConfigMapping, otherwise the config groups cannot be analyzed as part of config mappings. This will go away in the future.
• then, the hierarchy here is quite weird with some methods overriding others, which is fine, except this is not properly handled in the config doc generator. For now, I just ignored the ones from the parent, but ideally, we should override them properly in the config doc generator.
• also I removed some inherited methods from GrafanaConfig and I'm not yet sure if it will break something so creating as draft.

Fixes #41285

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 226f281.

✅ 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.

[alesj]

The hierarchy stuff, with dups, was to handle previous behavior, which didn't know about hierarchy.
But afair, this was fixed by @radcortez , right?

[alesj]

Otherwise, this LGTM (pun intended ;-).

[radcortez]

The hierarchy stuff, with dups, was to handle previous behavior, which didn't know about hierarchy.
But afair, this was fixed by @radcortez , right?

I have a vague idea that we have some issue with that, but I can't remember exactly. Regardless, I believe any hierarchy mapping should work just fine.