fix(release): publish github release after package publish

[Niraj12chaudhary]

Issue for this PR

Closes #16088

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Fixes release ordering in script/publish.ts.

Before this change, the GitHub release was marked non-draft (gh release edit ... --draft=false) before npm package publishing finished.
If plugin publish failed after that, users could see a released OpenCode version while @opencode-ai/plugin for the same version was still missing on npm.

This PR moves the gh release edit ... --draft=false step to the end of the script, after CLI/SDK/plugin publish steps complete.

Why this works: release visibility now depends on successful package publish completion, so we avoid “released version but missing npm package” mismatch.

How did you verify your code works?

• Reviewed script/publish.ts flow and confirmed release publication step now runs after:
  • packages/opencode/script/publish.ts
  • packages/sdk/js/script/publish.ts
  • packages/plugin/script/publish.ts
• Checked git diff to ensure only this ordering change was made.

Screenshots / recordings

N/A (release script change)

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR