fix(ci): use app token for releases and consistent CHANGE.md formatting

[JasonXuDeveloper]

Summary

Fixes two issues with the release workflow:

1. Release created by wrong bot

Before: Releases were created by github-actions[bot] because GITHUB_TOKEN was used

After: Releases will be created by jengine-release-bot[bot] using the app token

+ - name: Generate GitHub App Token
+   uses: actions/create-github-app-token@v1
+   with:
+     app-id: ${{ secrets.RELEASE_APP_ID }}
+     private-key: ${{ secrets.RELEASE_APP_PRIVATE_KEY }}

- GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ GH_TOKEN: ${{ steps.generate-token.outputs.token }}

2. Inconsistent CHANGE.md formatting

Before: Conventional commits were bolded, others were not

- **Add feature X** (ci)      <- bold
- Fix something Y             <- not bold

After: All entries use consistent formatting (no bold)

- Add feature X (ci)
- Fix something Y

Test plan

• Merge this PR
• Delete 1.0.8 tag and release
• Run release workflow with core_version=1.0.9 and util_version=1.0.3
• Verify release is created by jengine-release-bot[bot]
• Verify CHANGE.md entries have consistent formatting

🤖 Generated with Claude Code

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[github-actions]

Unity Test Results

✅ EditMode: All tests passed
✅ PlayMode: All tests passed

Unity Version: 2022.3.55f1
Project Path: UnityProject

✅ All tests passed! The PR is ready for review.

View workflow run

Click here to view the full workflow run