[v0.8.1-alpha] Publish Abada Engine to Maven Central

[bashizip]

📦 Publish Abada Engine to Maven Central

Description

We need to publish the Abada Engine to Maven Central so that it can be consumed easily by external projects as a standard Maven dependency.
This task is part of the 0.7.0-alpha milestone.

---

🛠️ Tasks

• Create an account on Sonatype JIRA
• Request access for the groupId io.macrodev
• Generate a GPG signing key
• Upload GPG public key to a key server (e.g., keyserver.ubuntu.com)
• Update pom.xml:
  • Add full project metadata (name, description, URL)
  • Add license information (MIT License)
  • Add developers section
  • Add SCM (source control) section
  • Configure distribution management for OSSRH
  • Add plugins for GPG signing, source JAR, and javadoc JAR
• Create a ~/.m2/settings.xml file with OSSRH credentials and GPG key info
• Test publishing a SNAPSHOT version to OSSRH snapshot repository
• Finalize and deploy the first RELEASE version (0.7.0-alpha)
• Close and release the staging repository on OSS Nexus UI
• Confirm the artifact is visible on Maven Central (https://search.maven.org/)

---

📋 Notes

• Initial version to publish: 0.7.0-alpha
• Group ID: dev.abada`
• Maven Central sync may take approximately 10–30 minutes after release.
• Future step: Automate releases with GitHub Actions.

---

🏷️ Labels

enhancement, release, maven-central, publishing