Document the build lifecycle and troubleshooting

[ppkarwasz]

Summary

Adds two Antora documentation pages that explain what the Logging Parent POM adds to a Maven build, addressing the long-standing gap that features.adoc only lists bundled plugins.

• build-lifecycle.adoc: a phase-by-phase overview table plus sections on:
  • the checks (Maven & Java version, order-independent dependency resolution, code style, changelog validation, Error Prone, SpotBugs + FindSecBugs, license validation, BND baseline), each tagged with its phase and origin (this POM vs. the ASF Parent POM);
  • the generated artifacts (OSGi manifest, JPMS descriptor, ServiceLoader descriptor, CycloneDX SBOM, and the inherited META-INF/{LICENSE,NOTICE,DEPENDENCIES});
  • the POM transformations (CI-friendly ${revision} resolution and BOM flattening);
  • the opt-in profiles: build modifiers (release, coverage, apache.snapshots) and commands (changelog-release, distribution, deploy).
• troubleshooting.adoc: debugging recipes for the two checks that are hardest to diagnose:
  • the BND baseline API-compatibility check (how to read the delta report, the MICRO/MINOR/MAJOR fixes, and the rationale behind the package-versioning convention);
  • the requireUpperBoundDeps order-independent dependency resolution check (how to read the error and whether to pin, bump, or unpin).

Both troubleshooting recipes use real error output captured by reproducing the failures locally.

Both pages are wired into the site navigation under a new "Build" group.

Notes

• Website/docs only; no change to the released parent POM artifact, so no changelog entry is included.
• A site-lifecycle page is intentionally deferred for a follow-up; its references were removed from this change.

🤖 Generated with Claude Code