chore: verify Maven Central namespace for new groupId

[wphillipmoore]

Context

The migration from wphillipmoore to mq-rest-admin-project changed the Maven groupId from io.github.wphillipmoore to io.github.mq-rest-admin-project. The next release will attempt to publish under this new groupId to Maven Central.

Current state

• pom.xml groupId: io.github.mq-rest-admin-project
• artifactId: mq-rest-admin (unchanged)
• Publishing via central-publishing-maven-plugin 0.10.0 with publishingServerId: central and autoPublish: true
• GPG signing configured via maven-gpg-plugin
• CD workflow uses vergil-project/vergil-actions/.github/workflows/cd-release.yml@v2.0 with registry-publish: true
• Previous releases were published under io.github.wphillipmoore

What needs to happen

1. Namespace verification — Maven Central requires namespace ownership verification for new groupIds. The namespace io.github.mq-rest-admin-project must be claimed and verified at central.sonatype.com. This typically involves proving ownership of the corresponding GitHub organization (mq-rest-admin-project) via a DNS TXT record or a temporary verification repo.

2. Credential configuration — Verify that the GPG key and Sonatype credentials used by CI can publish under the new namespace. The central server ID in the publishing plugin must resolve to valid credentials in the workflow environment.

3. Test publish — Before cutting a real release, consider a dry run or snapshot to validate the full pipeline under the new groupId.

4. Consumer migration note — Existing consumers using io.github.wphillipmoore:mq-rest-admin will need to update their dependency coordinates. Consider documenting this in the release notes for the first release under the new groupId.

Previous coordinates (for reference)

<dependency>
    <groupId>io.github.wphillipmoore</groupId>
    <artifactId>mq-rest-admin</artifactId>
</dependency>