fix: Maven Central publishing after OSSRH migration

The new Central Portal has stricter artifact validation than the old
OSSRH. This fixes the deploy step that runs when release:prepare pushes
the release commit back to main:

- Add <name> to child POMs (now required by Central Portal)
- Change test module to pom packaging so it no longer produces an empty
  JAR that fails Central validation
- Remove skipNexusStagingDeployMojo from test module (was preventing
  deploy-at-end from triggering since test is the last reactor module)

Signed-off-by: Gal Ovadia <ggalovadia@gmail.com>

Author: ovadiagal

api/pom.xml

@@ -9,6 +9,7 @@
     </parent>
 
     <artifactId>api</artifactId>
+    <name>api</name>
 
     <properties>
         <checkstyle.skip>true</checkstyle.skip>

cache/pom.xml

@@ -9,6 +9,7 @@
     </parent>
 
     <artifactId>cache</artifactId>
+    <name>cache</name>
 
     <dependencies>
         <dependency>

server/pom.xml

@@ -9,6 +9,7 @@
     </parent>
 
     <artifactId>server</artifactId>
+    <name>server</name>
 
     <dependencies>
         <dependency>

test/pom.xml

@@ -9,10 +9,11 @@
     </parent>
 
     <artifactId>test</artifactId>
+    <name>test</name>
+    <packaging>pom</packaging>
 
     <properties>
         <maven.deploy.skip>true</maven.deploy.skip>
-        <skipNexusStagingDeployMojo>true</skipNexusStagingDeployMojo>
     </properties>
 
     <dependencies>