Add support for primary rate limits about go-github-ratelimit

[gofri]

Apparently, code search rate limits behave like primary rate limits (i.e., the response is a primary rate limit error),
but their reset time is really short (1min).
That means that when adding support for primary rate limit, it also needs to support sleep by default for short periods.

@NorseGaud @abhijit-hota - I haven't forgotten about this issue and I'm planning to do it soon. My days are pretty busy now, and I'm finishing off async-pagination support now, and then I'm gonna address this one.
https://github.com/gofri/go-github-pagination

[gofri]

@Sawthis
I wish.
I'm really over my head with work and my other duties. Haven't forgotten about it, and I hope that I'll be able to make the first step next week

Edit: not sure if you heard the news about Iran attacking israel, but there might be some more delay after all 😅

[NorseGaud]

bump :)

[gofri]

@NorseGaud nice to see interest. I'd love to hear more about your use case (and hopefully, I'll get to it soon)

[gofri]

Following the discussion in #9 - will be implemented using x-ratelimit-resource (and perhaps a fallback for endpoint-based heuristics, because x-ratelimit-resource isn't officially documented).
Will probably go into v2.0.0 to allow a clearer API, including:

• Renaming the options to be clearer on secondary vs primary rate limit.
• Support for returning a dedicated error instead of sleeping (probably different error type for secondary/primary -- keeping sleep the default for secondary, and return error as the default for primary).
• WithXXX for the options of injected (instead of the lazy approach of single options struct used now).

[Sawthis]

@gofri any update on this topic?