Update GitHub Actions best practices: use OSBotify token as little as possible

[roryabraham]

Problem

Using OSBotify token requires repo secrets and extra steps. Sometimes it's necessary, such as when committing or pushing code in our CI.

Solution

Precisely nail down the scenarios when OSBotify is needed. When he's not, use the standard github.token instead.

[roryabraham]

Stopped using it for checklists, and that's a start. But there's a lot of usages currently.

Another example when the GitHub Actions token doesn't work is when accessing stuff at the org level like GitHub teams

[roryabraham]

No update, lower priority item

[roryabraham]

Created one PR to help move this in the right direction and eliminate a source of flakiness: #32848

[roryabraham]

No update, have been OOO

[roryabraham]

No update here

[roryabraham]

No update

[roryabraham]

Going to close this since we haven't been seeing nearly as many stability issues with the OSBotify bot token