Fabisev/automating mvn deployment

[fabisev]

Issue #, if available:

Description of changes:

Replaces the manual mvn deploy release with GitHub Actions release pipelines that build, test, sign, and publish CI-validated artifacts to Maven Central.

• release.yml: workflow_dispatch pipeline for the six pure-Java modules. Pinned JDK 8, mvn verify gate, then release:prepare/release:perform with a publish-safe ordering (prepare locally, publish, then git push --atomic only after publish succeeds; failure rolls back the runner and never modifies the remote). Repo-wide release concurrency group so releases never overlap.
• release-runtime-interface-client.yml: dedicated RIC pipeline. RIC ships a JNI native library for four targets plus a main JAR, so each native library is built on a runner of its own architecture (x86_64 on ubuntu-latest, aarch_64 on ubuntu-24.04-arm) instead of QEMU emulation, then one job assembles all artifacts and publishes them.
• POM changes across all modules: SNAPSHOT versions, maven-release-plugin configuration, SCM developerConnection, and autoPublish=true.
• Credentials are fetched at runtime via GitHub OIDC

Testing done:

Validated locally with act (GitHub Actions run in a container)

• Workflow mechanics (dry-run of release.yml): checkout, pinned JDK 8, mvn verify, and release:prepare -DdryRun pass; correct release tag and next-development version bump.
• Publish chain (against a personal Sonatype namespace I control, with auto-publish disabled and the deployment dropped afterward): GPG signing, token auth, upload, and Sonatype validation all succeed with no errors, exercising the same signing/settings/publishing mechanic the real workflow uses.
• log4j2 module correctness (built on pinned JDK 8): the jar contains the Log4j2Plugins.dat descriptor, classes are Java 8 bytecode, and the descriptor unit test passes.
• RIC native build: the arm64 classifier jar was built on JDK 8 and contains a correct ARM aarch64 ELF shared object.
• RIC multi-artifact publish shape: a main jar plus four classifier jars deploy as a single deployment and validate with no errors.
• Credential fetch (read-only)

Not exercisable outside a real run in this repo: the live token exchange and the CI build-matrix assembly. These will be covered by the first dry-run (skip_publish: true) after merge.

Target (OCI, Managed Runtime, both): N/A

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.38%. Comparing base (371508e) to head (e3223b5).

Additional details and impacted files

@@                        Coverage Diff                         @@
##             feat/invocation-id-cross-wiring     #626   +/-   ##
==================================================================
  Coverage                              65.38%   65.38%           
  Complexity                               212      212           
==================================================================
  Files                                     34       34           
  Lines                                    991      991           
  Branches                                 143      143           
==================================================================
  Hits                                     648      648           
  Misses                                   290      290           
  Partials                                  53       53           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.