Fix git push in publish workflow

[bquorning]

The final git push is failing because of our branch protection rules: https://github.com/rubocop/rubocop-rspec/actions/runs/8561970997/job/23464311900

@ydah suggested maybe the solution is as follows:

• creating a service account user that has read-write access to repo
• create a pat for that service account
• add the service account to the bypass protection rules in the branch
• create a repo secret that contains the PAT token
• push using the created service account

[bquorning]

Fixed by #1869.

[bquorning]

In #2007 I added permissions for actions to the workflow, but they still don’t run on the created pull requests. A colleague pointed me to https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#workarounds-to-trigger-further-workflow-runs, and the easiest workaround listed there is to just have a human close and reopen the PR.

Or have the script open a draft PR, and then the actions will run when a human marks it as Ready for review. But we wouldn’t get notifications for a draft PR.

The more correct solution would be to create a machine account with collaborator access on the RuboCop organization (or this repo specifically) and create a PAT that we can use when opening the PR.