Fix Maven Central publication metadata

[AhmedNMahran]

Summary

This updates the publishing configuration so mobile-sync can be published consistently to Maven Central as a single top-level Android/KMP artifact for downstream consumption.

What changed

• normalized publication group/version to use the repo release version from gradle.properties
• fixed stale project metadata URL from mobile-data to mobile-sync
• enabled Maven Central publication for sync-pipelines
• enabled Maven Central publication for mutations-definitions
• fixed umbrella publication coordinates so it no longer publishes as syncengine
• changed the published artifact id for sync-pipelines to mobile-sync

Why

Before this change:

• sync-pipelines and mutations-definitions had signing configured but were not opted into Maven Central publication
• several modules were publishing with a stale hardcoded version from the version catalog instead of the actual repo release version (0.0.3)
• umbrella was configured with the wrong artifact id (syncengine)
• some POM metadata still pointed at the old repo URL
• Android consumers would have had to depend on sync-pipelines rather than a clean top-level mobile-sync artifact

Result

For Android consumers, the intended dependency is now:

implementation("com.quran:mobile-sync:0.0.3")

The underlying modules (auth, persistence, syncengine, mutations-definitions) remain published separately and are pulled transitively through the top-level artifact.

Validation

• verified Maven Central publish tasks now exist for:
  • auth
  • mutations-definitions
  • persistence
  • sync-pipelines
  • syncengine
  • umbrella
• regenerated publication metadata for sync-pipelines
• verified generated POM metadata resolves to:
  • groupId = com.quran
  • artifactId = mobile-sync
  • version = 0.0.3
• ran ./gradlew publishToMavenLocal to validate publication wiring
• current remaining blocker is expected and external to repo code:
  • signing credentials are not configured on this machine (no configured signatory)

Follow-up

Android consumers should only need:

implementation("com.quran:mobile-sync:0.0.3")

However, because the top-level artifact depends transitively on the underlying published modules, releasing the full Android/KMP surface requires publishing them as well:

./gradlew \
  :mutations-definitions:publishAndReleaseToMavenCentral \
  :syncengine:publishAndReleaseToMavenCentral \
  :persistence:publishAndReleaseToMavenCentral \
  :auth:publishAndReleaseToMavenCentral \
  :sync-pipelines:publishAndReleaseToMavenCentral

If we also want the iOS umbrella artifact on Maven Central, add:

:umbrella:publishAndReleaseToMavenCentral