ci: generate CHANGELOG on release draft

[denischilik]

Adds the ROKT generate-changelog composite action to Release – Draft after the Maven Local smoke step.

• Runs with kits-path: kits for Core vs Kits grouping.
• Omits explicit tag-prefix so semver matches VERSION and GitHub release tags.

[cursor]

PR Summary

Medium Risk
Updates the release-draft GitHub Actions workflow, which can affect the release preparation pipeline and PR contents if the changelog generation step fails or produces unexpected output.

Overview
The Release – Draft workflow now runs a pinned ROKT/rokt-workflows/actions/generate-changelog step after the Maven-local smoke publish to automatically generate/update CHANGELOG.md for the bumped version (excluding chore/ci/test/build types and grouping via kits-path: kits).

This changelog generation happens before the release PR is created, so the resulting release branch/PR will include the changelog updates alongside the version bump.

^{Reviewed by Cursor Bugbot for commit e4e42c5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c0bf854. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud