oss-prow alert is very flaky on GitHub token usage

[chaodaiG]

Current alert is off when the predicted token consumption is over the rate limit before next token reset, this could happen when there is a sharp drop early after token reset, which doesn't necessarily mean the slope would continue like this. This had happened quite frequently in the past few weeks and it's very noise.

An idea fixing this would be to add another condition like trigger only when the token consumption is above 80%

[chases2]

Hook, Tide, and Crier seem to be using an anonymous GitHub client. That seems like it would make this issue worse:

component: "tide"
file: "k8s.io/test-infra/prow/flagutil/github.go:260"
func: "k8s.io/test-infra/prow/flagutil.(*GitHubOptions).githubClient"
level: "warning"
msg: "empty -github-token-path, will use anonymous github client"
}

[chaodaiG]

Hook, Tide, and Crier seem to be using an anonymous GitHub client. That seems like it would make this issue worse:

This warning is false alert, these components use GH app for authenticating, I'm fixing this false warning in kubernetes/test-infra#26322