feat: add Claude Code skill for managing release tracking issues

Adds a gh-issue-release skill that automates post-release tasks:
creating the next version's tracking issue, updating the current
version's issue with completed task links, and closing it.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
---
chore: exclude .claude directory from license header checks

Co-Authored-By: Claude Opus 4.6 <[email protected]>

* fix: add explicit Automatic-Module-Name to httpclient modules

* docs: add CHANGELOG entry for #7460

* fix: remove chnanges that are not required

---------

Co-authored-by: UniZKTech
Co-authored-by: Ashish Thakur <[email protected]>

… modules

The auto-derived JPMS module names from JAR filenames don't match the
actual Java package names and cause a collision between httpclient-vertx
and httpclient-vertx-5 (both derive "kubernetes.httpclient.vertx").
Add a file-activated profile in the parent POM that sets the module name
from a jpms.module.name property, and add a test module to verify the
manifest entries and JPMS module resolution.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>

The central-publishing-maven-plugin deploys each module individually
for SNAPSHOTs. When BOMs deploy in the same reactor, they may fetch
metadata for recently deployed artifacts and hit a server-side
inconsistency window between maven-metadata.xml and its checksum
file, causing checksum validation failures. Splitting the deploy
into two invocations avoids this race condition.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>

The maven-dependency-plugin:copy goal resolves artifacts from
repositories, not the reactor. Without explicit dependencies on the
httpclient modules, parallel builds (-T) fail when snapshots aren't
published to the remote repository.

Signed-off-by: Marc Nuri <[email protected]>

Remote SNAPSHOT metadata (maven-metadata.xml) on the Sonatype server
can have persistent checksum inconsistencies. The -C (strict checksums)
flag in MAVEN_ARGS makes these fatal. Adding -c (lax checksums) to the
deploy step overrides this, allowing the build to warn and continue
instead of failing.

Also reverts the split deploy (separate BOM invocation) since lax
checksums makes it unnecessary.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>

The release profile declares BOM modules under target/classes/ which
are generated during the build. Dependabot scans all profiles and
fails when it can't find these pom.xml files in the repository.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>

Signed-off-by: Marc Nuri <[email protected]>

Maven's CLI parses -C and -c with if/else-if, so -C always wins when
both are present. The previous fix appended -c to the deploy command
but it was silently ignored because -C was already in MAVEN_ARGS.

Move -c into MAVEN_ARGS directly, replacing -C, so lax checksums apply
to the entire snapshot build including the deploy phase.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

Style checks and model generation are prerequisites that must pass
before a PR is mergeable. When they fail, this cancels all other
in-progress and queued workflow runs for the same commit to avoid
wasting CI resources on builds and e2e tests that aren't needed.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>