A peter-evans/create-pull-request 403 is worth reading twice, because the step does two different privileged things and only one of them usually fails. If the branch appears in the repository, the push succeeded and what was refused was the pull request itself.
Two privileged calls in one step. Whether the branch exists afterwards tells you which of them was refused, and they are governed by different things.
What this error means
The action runs, the commit is made, and the branch exists afterwards. The step still fails, and the message is a complete sentence about GitHub Actions not being permitted to create or approve pull requests.…