[gwr0-0]

Problem

The root POM still declared an OSSRH-style <distributionManagement>. With -Pci,gpg,
central-publishing-maven-plugin (extensions=true) replaces maven-deploy-plugin through its
lifecycle participant and publishes via publishingServerId; release deploys never read that
block. Keeping it is dead configuration and suggests a deploy path that is no longer used.

Change

Remove the <distributionManagement> block. No replacement comment: the gpg profile already
shows the Central plugin configuration, and the rationale is in the commit message.

Why this is safe

• Release deploys: both release.yml and snapshot.yml run with -Pci,gpg, so the Central
  plugin is active. Its extensions=true lifecycle participant clears maven-deploy-plugin's
  execution and injects the Central publish goal, so deploy does not read
  distributionManagement at all.
• Snapshot deploys: before this change snapshots used the removed <snapshotRepository>;
  after it the plugin falls back to the Central snapshots repository. The URL
  (https://central.sonatype.com/repository/maven-snapshots/) and server id (central) are
  identical before and after — verified against the plugin 0.12.0 sources
  (Constants.CENTRAL_SNAPSHOTS_URL_DEFAULT_VALUE, ArtifactDeferrerImpl.getDeploymentRepository).
• Bare ./mvnw deploy without the gpg profile is not a supported publishing path; it now
  fails explicitly in maven-deploy-plugin ("repository element was not specified") instead of
  silently using a stale URL. Release and snapshot publishing are workflow-driven
  (release.yml / snapshot.yml); a dedicated release procedure page lands in the follow-up PR.
• Rollback: revert this commit; it is configuration-only.

Verification

• git show HEAD:pom.xml | grep -n distributionManagement → no output (the block is gone).
• git diff --check clean; single commit on top of 321ec905d; POM diff is a pure deletion (−10).
• No build change expected: deployment paths are exercised by the Snapshot workflow on pushes
  to main/spring-boot-3; runtime deploy cannot be exercised locally (no Central/GPG credentials).

Notes

• No CHANGELOG.md entry: release tooling only, no API/behavior change for users.
• Not included here: ignoring release.properties/*.releaseBackup. release:clean already
  removes them, and leaving them unignored keeps the dry-run working-tree assertion honest.