Deploy first version 0.0.1-SNAPSHOT in Maven Central

[Javiervva]

This issue aims to track the process of acquiring a new groupId for our project, net.nexus-flow, in Maven Central. This is a necessary step to ensure that we can publish our packages to Maven Central under our own domain.

Action Items:

1. Open a ticket in the Maven Central issue tracker to request the new groupId net.nexus-flow.
2. Provide the necessary verification to prove domain ownership of nexus-flow.net.
3. Ensure that our project's Gradle configuration aligns with Maven Central's requirements, including artifact naming conventions, versioning, and metadata.
4. Update our CI/CD pipeline (GitHub Actions) to automate the deployment process once our groupId is approved and configured.

[Javiervva]

The request to obtain a custom groupid is currently in progress. You can monitor its status through this link: Sonatype Ticket.

Additionally, it's worth noting that the domain 'nexus-flow.net' has already been acquired.

[Javiervva]

Group ID Acquisition Completed.

Our group ID, net.nexus-flow, is now established. The next steps involve finalizing the tasks in the milestone. Additionally, we need to set up our CI/CD pipeline using GitHub Actions and configure our build automation tool, Gradle, along with the necessary settings for publishing to Maven Central.