fix(ci): explicitly trigger Maven release workflow from release-please

[KaviarasuSakthivadivel]

GITHUB_TOKEN-triggered events don't cascade to prevent recursive workflows. When release-please creates a release using GITHUB_TOKEN, the 'release: published' event is suppressed and won't trigger the Maven Central publish workflow.

Solution: explicitly trigger release.yml via workflow_dispatch when a release is created.

Ref: https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.10%. Comparing base (6081077) to head (892efa4).

Additional details and impacted files

@@            Coverage Diff            @@
##               main     #161   +/-   ##
=========================================
  Coverage     83.10%   83.10%           
  Complexity     1667     1667           
=========================================
  Files           119      119           
  Lines          4641     4641           
  Branches        493      493           
=========================================
  Hits           3857     3857           
  Misses          560      560           
  Partials        224      224           

Components	Coverage Δ
JDBC Core	84.10% <ø> (ø)
JDBC Main	40.69% <ø> (ø)
JDBC HTTP	90.30% <ø> (ø)
JDBC Utilities	65.25% <ø> (ø)
Spark Datasource	∅ <ø> (∅)

🚀 New features to boost your workflow:

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

[j10t]

Thanks for taking this. The wiring is correct end-to-end (verified release.yml has matching workflow_dispatch/tag_name input, release-please-action@v4 emits both outputs as named, no recursion risk).

One change before merge: the script: block interpolates ${{ needs.release-please.outputs.tag_name }} directly into inline JS, which is the pattern GitHub flags as script-injection-prone.