Move 'composite builds' into 'Authoring Gradle Builds' chapterComposite builds are primarily a feature to organize your ownbuilds into multiple independent units.They can be used to substitute a module dependency with a localfork. Thus the chapter is now referenced from dependency managementin the section where we describe the different types of dependenciesthat are supported.
Use a flatten directory for all adoc filesThis commit reworks how asciidoctor files are processed,by allowing to structure docs using subdirectories, whilemaintaining consistent locations for resources, images, samples,...This works by flattening all adoc files into a resourcesdirectory before processing. It means that while we canuse a directory tree to organize docs, we must make surenot to use the same file name twice.This makes it possible to compose files more easily. Forexample, the dependency management docs can be read asa single file, or individual files, or as chapters.Technically speaking, we could remove the "userguideSinglePage"task, but it's kept just because it's significantly slowerto build.
Reshuffle dependency management docsThis commit reshuffle existing dependency management docsinto the new dependency management chapter. It's worth notingthat there's no new content at this point, nor any effort tomake it consistent. It just moves things around, and thereare still quite a few places where dependency management docsare found.It doesn't try to fix dead links either.