ci: Standardize SDK release failure telemetry

[marandaneto]

💡 Motivation and Context

Release workflow failures are currently reported with repo-specific PostHog event names or have gaps in pre-publish failure coverage. That would require separate Hog function handling per SDK and makes cross-SDK release failure monitoring harder.

💚 How did you test it?

• Parsed modified workflow YAML successfully.
• Ran git diff --check.
• Verified modified PostHog release failure events use posthog-sdk-github-release-workflow-failure and include the expected metadata.

📝 Checklist

• I reviewed the submitted code.
• I added tests to verify the changes.
• I updated the docs if needed.
• No breaking change or entry added to the changelog.

If releasing new changes

• Ran changeset generation for a release changeset file

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

This PR was prepared with Pi after a human requested consistent SDK release failure telemetry. The change is limited to GitHub Actions release workflow telemetry; no runtime SDK code is changed.

Changes:

• Updated .github/workflows/release.yml

• Use the shared posthog-sdk-github-release-workflow-failure event for SDK release failure telemetry.\n- Use latest pinned action versions for PostHog/posthog-github-action and PostHog/.github/.github/actions/slack-thread-reply.n- Include consistent metadata: repository, sdk, jobName, packageName, packageVersion, actionUrl, alertText, and alertContext.\n- Keep actionUrl pointing at https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}.

[greptile-apps]

_{Reviews (1): Last reviewed commit: "ci: standardize SDK release failure tele..." | Re-trigger Greptile}

[greptile-apps]

_{Reviews (2): Last reviewed commit: "ci: standardize SDK release failure tele..." | Re-trigger Greptile}