Support @WithUnnamedKey in documentation

[radcortez]

This adds the ability in the processor to generate config documentation where the unnamed and named keys of a Map are listed in the same section. This only works for @ConfigMapping and @WithUnnamedKey in a Map.

Example with the Hibernate Search Extension:

[yrodiere]

Thanks. I agree it does get crowded in the case of Hibernate Search but it's due to the very structure of the extension's configuration, which is perhaps too complicated.

In any case, it's much better that it was previously and IMO we should merge this step in the right direction. We could add CSS/javascript (a ... button, maybe?) at a later point to hide extra keys.

[quarkus-bot]

Failing Jobs - Building f32919f

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 19
✔️	Maven Tests - JDK 11
⌛	Maven Tests - JDK 11 Windows	Build	⚠️ Check →	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: extensions/scheduler/deployment 
! Skipped: extensions/quartz/deployment extensions/spring-scheduled/deployment integration-tests/devmode and 4 more

📦 extensions/scheduler/deployment

✖ io.quarkus.scheduler.test.ScheduledMethodTimeZoneTest.testScheduledJobs line 71 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

[yrodiere]

@gsmet Any way we could backport this to 3.2? That would make things simpler for me in hibernate-search-extras (see quarkiverse/quarkus-hibernate-search-extras#160 )

(asking because I see you added the backport label then removed it without backporting)

[radcortez]

I think it should be fine to backport.