🐛 Bug: Release-it release commits blocked by new repository rulesets

[JoshuaKGoldberg]

Bug Report Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Expected

When the Release flow has a change to the package.json, it should be able to commit it in CI.

Actual

The ruleset I added in #1788 & tried to fix in #1791 is still not allowing the CI job to push.

Additional Info

I suspect the right long-term fix would be GitHub Deploy Keys. But for now I think I'm just going to remove the requirement that changes be sent in PRs.

💖

[JoshuaKGoldberg]

😕 removing the requirement of a PR still leaves the requirement of passing CI status:

ERROR remote: error: GH013: Repository rule violations found for refs/heads/main.        
remote: Review all repository rules at https://github.com/JoshuaKGoldberg/cta-publish-testing/rules?ref=refs%2Fheads%2Fmain        
remote: 
remote: - 5 of 5 required status checks are expected.        

[JoshuaKGoldberg]

I think I figured it out. The release job should be running as whatever user+permissions are provided by the ACCESS_TOKEN secret. But they're not getting those permissions.

I found references in a few StackOverflow answers -most helpfully, https://stackoverflow.com/questions/71669640/bypass-required-status-checks-in-github- to using the token in actions/checkout. And that seemed to fix it!