[chore] Bump rate at which we process issues

[TylerHelmuth]

Description:
This PR attempts to increase the amount of issues/PRs the Close State Issues/PRs actions can process by:

• increase the number of operations it may perform. We have at least 1000 per hour via actions, so 400 an hour from this job should still leave plenty for the ping-code-owners and other jobs that interact with our PRs/Issues.
• Increase how many times it runs a night. This is a temporary solution to try and get us caught up.
• Allow manually triggering the job. I am hoping to use this to test and to manually run the job while we try an catch up.

[TylerHelmuth]

Added a rate_limit check before and after to monitor how this change affects our limits. Output will look something like this:

❯ curl https://api.github.com/rate_limit
{
  "resources": {
    "core": {
      "limit": 60,
      "remaining": 59,
      "reset": 1685127794,
      "used": 1,
      "resource": "core"
    },
    "graphql": {
      "limit": 0,
      "remaining": 0,
      "reset": 1685128196,
      "used": 0,
      "resource": "graphql"
    },
    "integration_manifest": {
      "limit": 5000,
      "remaining": 5000,
      "reset": 1685128196,
      "used": 0,
      "resource": "integration_manifest"
    },
    "search": {
      "limit": 10,
      "remaining": 10,
      "reset": 1685124656,
      "used": 0,
      "resource": "search"
    }
  },
  "rate": {
    "limit": 60,
    "remaining": 59,
    "reset": 1685127794,
    "used": 1,
    "resource": "core"
  }
}

[evan-bradley]

Those numbers look a little off, the docs say we should have a larger request count than that. Could you try printing the headers from a request like this?

curl --request GET \
          --include \
          --silent \
          --show-errors \
          --dump-header - \
          --url https://api.github.com/repos/${{ github.repository }}/issues \
          --header 'authorization: Bearer ${{ secrets.GITHUB_TOKEN }}' \
          --header 'content-type: application/json' \
          --output /dev/null \
          --fail

[TylerHelmuth]

@evan-bradley Those numbers are from my own token which is why they are so low.

But looking at the command again maybe it isn't smart enough to use our token. I'll update the command.

[evan-bradley]

Got it, thanks. Looks like that API is the right one to use too, let's go with that.

[TylerHelmuth]

@evan-bradley here is what it looks like run in my fork, so I'm not confident in it anymore: https://github.com/TylerHelmuth/opentelemetry-collector-contrib/actions/runs/5093968840/jobs/9157205402

[TylerHelmuth]

I switched to gh cli and I think thats much more reliable: https://github.com/TylerHelmuth/opentelemetry-collector-contrib/actions/runs/5093988300/jobs/9157251383

[evan-bradley]

Agreed, looks better. I think the issue was that the auth token was missing on the curl request.