Merging main into develop after release fails due to branch protection rules

[asjohnston-asf]

Historically we've used the tools-bot user's personal action token to perform this merge and added them to the "allow these users to bypass branch protection rules" list.

We're trying to move toward using secrets.GITHUB_TOKEN over the bot token; it's not clear how to bypass branch protection rules in this situation.

[asjohnston-asf]

Rolled back to using TOOLS_BOT_PAK over GITHUB_TOKEN after encountering this issue as well as the issue described at asfadmin/grfn-gdal-api#53