Fix annoying "split package" build warnings

[adutra]

Is your feature request related to a problem? Please describe.

When building Polaris, we often see an annoying message printed many times to the console, e.g.:

Detected a split package usage which is considered a bad practice and should be avoided. Following packages were detected in multiple archives: 
- "org.apache.polaris.service.quarkus.catalog.io" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.metrics" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.legacy" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.persistence" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.storage" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.config" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.tracing" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.logging" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.context" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.ratelimiter" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.auth" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]
- "org.apache.polaris.service.quarkus.task" found in [org.apache.polaris:polaris-quarkus-service:1.0.0-incubating-SNAPSHOT]

I don't think we have truly split packages in Polaris. The above is likely a false positive. This can be seen by the number of conflicting artifacts: there is always only one artifact. This probably hints at 2 or more artifacts produced by the same module, having the same name. One possible culprit would be the artifacts created by the distribution plugin.

Related discussion: quarkusio/quarkus#19030 (comment)

Describe the solution you'd like

No more annoying messages.

Describe alternatives you've considered

No response

Additional context

No response