fix(build): don't skip deploying flash-extensions' own POM

Its maven-deploy-plugin was configured with <skip>true</skip>, so the
first successful publish-maven.yml run deployed flash-parent, flash,
and every flash-ext-* jar to Gitea's Maven registry, but not
flash-extensions itself — the pom-packaging aggregator every
flash-ext-* submodule's effective POM inherits from via <parent>.
Remote consumers (Pathway's Docker build, resolving flash-ext-* from
the registry instead of a local ~/.m2 install) couldn't resolve that
parent POM and failed with "artifacts could not be resolved:
flash-extensions:pom (absent)".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

flash-extensions/pom.xml

@@ -126,18 +126,13 @@
         </dependencies>
     </dependencyManagement>
 
-    <build>
+    <!--
-        <plugins>
+      No maven-deploy-plugin skip here (there used to be one): flash-extensions is a
-            <plugin>
+      pom-packaging aggregator with no jar of its own, but every flash-ext-* submodule's
-                <groupId>org.apache.maven.plugins</groupId>
+      effective POM inherits from it via <parent> — skipping its deploy meant remote consumers
-                <artifactId>maven-deploy-plugin</artifactId>
+      (anything resolving a flash-ext-* artifact from Gitea's Maven registry rather than a
-                <version>3.1.2</version>
+      local ~/.m2 install) couldn't resolve that parent POM at all. See
-                <inherited>false</inherited>
+      pathway/.gitea/workflows/docker-build.yml and pathway/docs/CI-CD.md.
-                <configuration>
+    -->
-                    <skip>true</skip>
-                </configuration>
-            </plugin>
-        </plugins>
-    </build>
 
 </project>