fix: fixed the profile for Artifact Registry deployment

[suztomo]

Defining the profile to publish artifacts to Artifact Registry.

The previous (reverted) attempt in #936 was wrong in that it missed this point when I used <activeByDefault>true</activeByDefault>:

This profile will automatically be active for all builds unless another profile in the same POM is activated using one of the previously described methods.

from https://maven.apache.org/guides/introduction/introduction-to-profiles.html.

This pull request now turns on the release-sonatype profile unless the artifact-registry-url property is defined. The property artifact-registry-url is only used for Artifact Registry publication.

Experiment

The java-shared-config repository was able to publish the artifacts to my Artifact Registry:

mvn deploy -P=release-gcp-artifact-registry -P=-release-sonatype
-P=-release-staging-repository -Dartifact-registry-url=artifactregistry://us-maven.pkg.dev/...

http://gpaste/5275049054175232

[burkedavison]

I don't think it's possible to chain profile activations/deactivations like this.

https://stackoverflow.com/a/2248552

Are you able to verify this works?

[suztomo]

This is not chaining profile activation (this is not relying on the line 145).

This activation relies on the fact that when we publish artifacts to GCP Artifact Registry using release-gcp-artifact-registry profile, -Dartifact-registry-url=... is always passed to the mvn command.

[suztomo]

I'll verify it works in the Kokoro release job.

[burkedavison]

Why have line 145, then?

[suztomo]

Line 145 is dummy value that tells the property is undefined.

[suztomo]

I'll verify it works in the Kokoro release job.

The release of this repository and google-auth-library-java (googleapis/google-auth-library-java#1593) succeeded.