Fix release version replacement appending old suffixes #192

Problem

The release/version update logic is incorrectly appending the new SDK version onto existing version suffixes instead of replacing the complete previous SDK version token.

Commit fd3fa58 demonstrates the bug: generated documentation and examples ended up with invalid chained artifact versions such as 1.0.0-beta-java.3-beta-java.2-beta-java.1.

Affected files shown in the commit

• README.md: 1.0.0-beta-java.2-beta-java.1 became 1.0.0-beta-java.3-beta-java.2-beta-java.1
• jbang-example.java: 1.0.0-beta-java.2 became 1.0.0-beta-java.3-beta-java.2
• src/site/markdown/cookbook/*.md: multiple //DEPS snippets were changed from 1.0.0-beta-java.2-beta-java.1 to 1.0.0-beta-java.3-beta-java.2-beta-java.1
• CHANGELOG.md: duplicate [Unreleased] comparison link definitions were added instead of replacing the existing one

Commit link: fd3fa58

Expected behavior

Version update automation should replace the full previous artifact version with the new release version. For example:

com.github:copilot-sdk-java:1.0.0-beta-java.2

should become:

com.github:copilot-sdk-java:1.0.0-beta-java.3

It should not become:

com.github:copilot-sdk-java:1.0.0-beta-java.3-beta-java.2

CHANGELOG.md should keep exactly one [Unreleased] comparison link, pointing from the latest release tag to HEAD.

Suggested fix

Review the release/version replacement script so it matches and replaces the complete Java SDK version token, including suffixes like -beta-java.N, rather than replacing only a prefix. Add coverage for README, JBang examples, site markdown snippets, and changelog link replacement to prevent chained versions and duplicate link definitions in future releases.