[SQBTC-1444] Update configuration to allow releasing modules independently

[ametke]

Independent Module Versioning and Release Process

TL;DR

Implement per-module versioning and automated release process for the Bitty City project.

What changed?

• Updated GitHub Actions workflow to support independent module releases via tagged prefixes (common-v*, innie-v*, outie-v*, outie-jooq-provider-v*)
• Moved version information from global gradle.properties to module-specific files
• Added comprehensive RELEASING.md documentation with step-by-step release instructions
• Created initial CHANGELOG.md for the outie module

How to test?

1. Create a tag with a module prefix (e.g., outie-v0.0.4) on the main branch
2. Verify the GitHub Actions workflow correctly:
   • Parses the module name and version from the tag
   • Builds and publishes only the specified module
3. Confirm the artifacts appear on Maven Central after publishing

Why make this change?

This change enables independent versioning and releasing of each module, providing several benefits:

• Modules can evolve at their own pace without forcing unnecessary releases of unmodified components
• Release process is more targeted and efficient
• Clear documentation ensures consistent releases across the team
• Changelog tracking improves visibility of changes between versions

[ametke]

• [SQBTC-1444] Update configuration to allow releasing modules independently #85 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.