Improve publishing and version management

[jacek-marchwicki]

Description

This pull request centralizes the Maven publishing configuration in the root build.gradle.kts file, removing hardcoded version and group IDs from individual module build.gradle.kts files. The project version is now dynamically set from an environment variable or defaults to 0.0.1-SNAPSHOT.

Additionally, the README.md has been updated to reflect these changes, using <version> placeholders for dependencies and providing a link to the GitHub releases page for specific versions. A new step has been added to the CI workflow to verify the publishing process by running ./gradlew publishToMavenLocal.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test addition or update
• CI/CD configuration change
• Other (please describe):

How to Test

The changes can be tested by running the CI pipeline. The added publishToMavenLocal step in .github/workflows/build.yml will verify that the publishing configuration is correct and the artifacts can be built and published locally.
Check if Link in the readme works.
Ensure JitPack succesfully build the project

Checklist

• My code follows the project's code style
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly (if applicable)
• I have added tests that prove my fix is effective or that my feature works

Additional Notes

This change simplifies version management and ensures consistency across all published modules.