Align modules and docs with repo manifest

[ascheman]

Further align modules and docs with repo manifest

cf. apache/maven-sources#18 and
support-and-care/maven-support-and-care#77

Following this checklist to help us incorporate your
contribution quickly and easily:

• Your pull request should address just one issue, without pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
• Run mvn site and examine output in target/site directory.
  Site will also be built on your pull request automatically and attached to GitHub Action result.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[Bukama]

In comparison to #786 I'm curious that the whole block got changed. Did you run mvn spotless:apply ?

[ascheman]

Nope, not explicitly, I just did a mvn site which includes a spotless:apply execution.

[hboutemy]

same feedback as apache/maven-sources#18: too many updates, it's impossible to review, we'll have to split (taking apart the spotless:apply that reformats)

in addition: the issue template in the description makes the interesting parts of the PR completely (= the "why" of the PR) invisible: we'll have to do somthing, because reviewing PRs with that massive boilerplate is a problem (not specific to the intent of this PR, I'm just writing down everything: I'll track that aspect with @slawekjaranowski separately)

[ascheman]

Split up to #790, #791, #792, #793, #794, #795, and #796