Extract GitHub Release creation to separate job

[AkaZver]

Summary

This PR extracts the GitHub Release creation step into a separate job that runs after successful publishing to both Gradle Plugin Portal and Maven Central.

Changes

Workflow Improvements

Before:

• GitHub Release was created as part of the \publish-gradle-portal\ job
• Release could be created even if Maven Central publishing failed

After:

• New \create-release\ job that depends on both \publish-gradle-portal\ and \publish-maven-central\
• GitHub Release is only created after successful publishing to both repositories
• Better separation of concerns - each job has a single responsibility

Behavior

The workflow still triggers only on tags on master branch:

• Both publish jobs verify the tag is on master
• If either publish job fails, the release job won't run
• Release notes are generated automatically using \gh release create --generate-notes\

Files Changed

• .github/workflows/main.yml\ - Extracted release creation to separate job

[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