fix: Use file-based activation for local-dev-javase profile

Changed the activation of the `local-dev-javase` profile in `maven/javase/pom.xml` to be based on the existence of the `${cn1.build.client.path}` file.
This prevents the profile from being active during the release build in GitHub Actions, which should fix the Maven Central deployment issue.

Author: shannah

maven/javase/pom.xml

@@ -53,7 +53,9 @@
         <profile>
             <id>local-dev-javase</id>
             <activation>
-                <activeByDefault>true</activeByDefault>
+                <file>
+                    <exists>${cn1.build.client.path}</exists>
+                </file>
             </activation>
             <dependencies>
                 <dependency>