chore: decide and implement version release strategy for 1.5.1-BETA

[pleberre]

Problem

Version 1.5.1-BETA has been in beta status since September 9, 2023 (16+ months). The version designation needs to be finalized.

Context

• Current version set in build.gradle.kts:28
• Major features added: Swift, Kotlin, Objective-C language support
• Extensive testing period (16+ months)
• Conventional commits tooling ready to merge (PR ci: adopt conventional commits with full tooling #4)
• Only documentation updates since version bump

Decision Required

Choose one of the following options:

Option A: Release as 1.5.1 final

• Pro: 16 months of stable testing
• Pro: No breaking changes since beta
• Con: Version number doesn't reflect conventional commits addition

Option B: Release as 1.6.0 final

• Pro: Reflects significant conventional commits infrastructure addition
• Pro: Clean version number for new release
• Con: Requires updating all documentation

Option C: Bump to 1.5.2-BETA or 1.6.0-BETA

• Pro: More time to address TODOs
• Con: Further delays stable release

Files Affected

• build.gradle.kts line 28

Questions for Decision

1. Should conventional commits infrastructure be considered a minor or major version bump?
2. Are there any known issues blocking a final release?
3. What is the criteria for removing BETA designation?

Acceptance Criteria

• Decision documented in this issue
• Version number updated in build.gradle.kts
• CHANGELOG.md created/updated with version changes
• Git tag created for release
• Documentation updated to reflect version