chore: use new GH_TOKEN secret

[robertsLando]

I have created an organization secret named GH_TOKEN with a fine grained organization token to be used in release workflow. It has restricted access only to this organization repo with content permissions (create releases and push commits).

This should allow the release workflow to successfully create the releases and bypass the main branch restrictions when pushing commits directly on main branch (chore(release): xxx commit)

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (main@e833f63). Click here to learn what that means.
Patch has no changes to coverable lines.

❗ Current head ec2408e differs from pull request most recent head 9c279b0. Consider uploading reports for the commit 9c279b0 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1625   +/-   ##
=======================================
  Coverage        ?   86.25%           
=======================================
  Files           ?       13           
  Lines           ?     1317           
  Branches        ?        0           
=======================================
  Hits            ?     1136           
  Misses          ?      181           
  Partials        ?        0           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[robertsLando]

@vishnureddy17 Just to inform you, I just did the 5.0.0-beta.2 release using the workflow and it worked now 🎉