The composite action runs clean deploy internally so the artifact
shuttle between build and deploy jobs was redundant and causing
download failures due to workspace conflicts after checkout.

Updated pom to use Central Portal snapshots

Child module had its own distributionManagement pointing to Artifactory.
Without overriding it in the profile, Maven hits Artifactory for metadata
during deploy and gets a 401. This profile redirects to Maven Central
snapshots when -P deploy-central-snapshot is active.

Testing snapshot deployment

…ntral-snapshot profile

central-publishing-maven-plugin with extensions=true replaces the default
deploy lifecycle, causing skipPublishing=true to result in a no-op deploy.
Explicitly re-bind maven-deploy-plugin to the deploy phase in both root and
child pom so artifacts are pushed directly to Central Snapshots URL.

…eploy-central-snapshot profile

With extensions=true in pluginManagement, central-publishing-maven-plugin
replaces the entire deploy lifecycle, making maven-deploy-plugin unreachable.
Setting extensions=false within this profile restores standard deploy behavior
so maven-deploy-plugin can push directly to the Central Snapshots URL.