fix: use GITHUB_TOKEN for release creation to resolve 403 error

[OzBenSimhonTraceloop]

…error

• I have added tests that cover my changes.
• If adding a new instrumentation or changing an existing one, I've added screenshots from some observability platform showing the change.
• PR name follows conventional commits format: feat(instrumentation): ... or fix(instrumentation): ....
• (If applicable) I have updated the documentation accordingly.

Summary by CodeRabbit

• Chores
  • Updated release workflow configuration to improve release process reliability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d42aafa9-c945-44a2-b3cf-ae535688b25c

📥 Commits

Reviewing files that changed from the base of the PR and between 17c7b7e and ab64051.

📒 Files selected for processing (1)

• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

The release workflow is updated to use the native GITHUB_TOKEN secret instead of a custom app token for release creation, with the bump-version job granted write permissions to repository contents.

Changes

Cohort / File(s)	Summary
GitHub Actions Release Workflow .github/workflows/release.yml	Added permissions block granting write access to contents for the bump-version job; changed GITHUB_TOKEN source from custom app token to native secrets.GITHUB_TOKEN in the Create Release step.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 A token swap, so clean and bright,
Permissions granted, workflow set right,
GitHub's own secret, now in the flow,
Releases shall dance, and onward we go! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and clearly describes the main change: using GITHUB_TOKEN instead of a custom token to fix a 403 permission error in release creation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch obs/fix-release-workflow-failures

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}