release-step-3: output docs release-notes URL instead of rendered changelog text

[Copilot]

This updates the release workflow to stop generating GitHub release notes from rendered changelog markdown and instead publish a direct link to Elastic docs for the released version. It removes the temporary docs-builder/sed workaround and aligns release-note content with the canonical docs page.

• What changed

  • Reworked generate-release-notes → Print Release Notes in .github/workflows/release-step-3.yml.
  • Replaced inline changelog rendering + post-processing with a single versioned docs URL written to GITHUB_OUTPUT.
  • Simplified the release-only generate-release-notes job by removing setup steps that are no longer needed after switching to a direct URL payload.

• Removed workflow logic

  • docs-builder changelog render invocation.
  • Temporary directory creation for rendered output.
  • Both sed cleanup steps that stripped heading artifacts.
  • Obsolete workaround comment tied to docs-builder behavior.
  • Unused Setup Gradle step.
  • Unused Docs builder setup step.

• Resulting release-notes payload

  • GitHub release body now resolves to the docs anchor for the released version.

- name: Print Release Notes
  id: print_release_notes
  run: |
    echo 'notes<<RELNOTESEOF' >> $GITHUB_OUTPUT
    echo "https://www.elastic.co/docs/release-notes/edot/sdks/java#${{ env.RELEASE_VERSION }}" >> $GITHUB_OUTPUT
    echo 'RELNOTESEOF' >> $GITHUB_OUTPUT

[SylvainJuge]

@copilot this part of the workflow is only executed at release time, it will not be triggered through regular CI build.

[Copilot]

@copilot this part of the workflow is only executed at release time, it will not be triggered through regular CI build.

Updated in 06d1245. I removed the now-unused Setup Gradle and Docs builder setup steps from generate-release-notes so this release-only path stays minimal and avoids unnecessary release-time dependencies.

[fr4nc1sc0-r4m0n]

LGTM