Gate release publishing with project checks

[fabian-barney]

Summary

• add the cognitive-java gate to the release workflow before publishing
• build and resolve the CLI jar during releases
• run the same Maven-source and Gradle-plugin crap-java gates used by CI before deployment steps

Closes #132

Verification

• mvn verify
• git diff --check

[Copilot]

Pull request overview

Adds the repo’s existing quality gates to the tag-based release workflow so releases can’t publish artifacts unless they pass the same cognitive-java and crap-java checks used in CI (closing #132).

Changes:

• Run mvn cognitive-java:check in the release workflow before any publish/deploy steps.
• Build and resolve the CLI shaded JAR during release, then run crap-java gates for Maven sources and the Gradle plugin sources.
• Ensure the Gradle wrapper is executable for the Gradle-plugin crap-java gate step.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.