Added uber minimum pom config in central publish (#1028)

Fix: Use minimal POM for Maven Central publishing
Restores the original behavior where both main and thin JARs are
published with the minimal POM (uber-minimal-pom.xml) instead of the
full POM with all dependencies.
Problem:
Since v1.0.8, the main JAR was being published with the full POM (all
dependencies)
Only the thin JAR was using the minimal POM
This caused dependency conflicts and larger POM files for users
Solution:
Add pomFile configuration to central-publishing-maven-plugin
Ensures both main and thin JARs use the minimal POM for publishing


## Testing


## Additional Notes to the Reviewer

---------

Signed-off-by: Nikhil Suri <nikhil.suri@databricks.com>

Author: nikhilsuri-db

NEXT_CHANGELOG.md

@@ -13,5 +13,6 @@
 - Fixed state leaking issue in thrift client.
 - Fixed timestamp values returning only milliseconds instead of the full nanosecond precision.
 - Fixed Statement.getUpdateCount() for DML queries.
+- Fixed Maven Central publishing to use minimal POM for both main and thin JARs, restoring behavior from v1.0.7 and earlier
 ---
 *Note: When making changes, please add your change under the appropriate section with a brief description.* 

pom.xml

@@ -698,6 +698,8 @@
              <publishingServerId>central</publishingServerId>
               <autoPublish>true</autoPublish>
               <waitUntil>published</waitUntil>
+              <!-- Use minimal POM for fat jar publishing -->
+              <pomFile>${project.basedir}/uber-minimal-pom.xml</pomFile>
             </configuration>
           </plugin>
         </plugins>