chore: skip java-samples using maven-deploy-plugin's skip (#11592)

* chore: skip java-samples using maven-deploy-plugin's skip

As part of the migration from OSSRH to Central Portal, we stop
using nexus-staging-maven-plugin, in favor of the (pure)
maven-deploy-plugin.
This means that if some modules are skipped using
nexus-staging-maven-plugin's skipNexusStagingDeployMojo property,
we need to convert it to maven-deploy-plugin's skip property.

* revert nexus-sonatype-maven-plugin

Author: suztomo

java-samples/native-image-sample/pom.xml

@@ -44,15 +44,6 @@
 
     <build>
         <plugins>
-            <plugin>
-                <groupId>org.apache.maven.plugins</groupId>
-                <artifactId>maven-deploy-plugin</artifactId>
-                <version>3.1.2</version>
-                <configuration>
-                    <skip>true</skip>
-                </configuration>
-            </plugin>
-
            <!-- This plugin enables building the application to a JAR *not* using native image compilation -->
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>

java-samples/pom.xml

@@ -5,6 +5,7 @@
     <name>Google Cloud Client Library for Java Samples</name>
     <artifactId>google-cloud-samples</artifactId>
     <groupId>com.google.cloud</groupId>
+    <!-- We do not release this module. The "-SNAPSHOT" version avoids accidental releases -->
     <version>0.1.0-SNAPSHOT</version>
     <packaging>pom</packaging>
     <modelVersion>4.0.0</modelVersion>
@@ -31,6 +32,19 @@
     <build>
         <pluginManagement>
             <plugins>
+                <plugin>
+                    <groupId>org.apache.maven.plugins</groupId>
+                    <artifactId>maven-deploy-plugin</artifactId>
+                    <configuration>
+                        <!--
+                          When we use OSSRH with nexus-staging-maven-plugin, this "skip" configuration
+                          is overridden and ignored by nexus-staging-maven-plugin.
+                          Once we start publishing artifacts via Central Portal using maven-deploy-plugin
+                          (without nexus-staging-maven-plugin), we no longer rely on skipNexusStagingDeployMojo.
+                        -->
+                        <skip>true</skip>
+                    </configuration>
+                </plugin>
                 <plugin>
                     <groupId>org.sonatype.plugins</groupId>
                     <artifactId>nexus-staging-maven-plugin</artifactId>