Add audit log rate limit category and make rate limit category getter public

[Letiste]

When calling https://api.github.com/rate_limit, the endpoint returns a audit_log rate limit category as well. This is used for /audit-log endpoints:

• https://docs.github.com/en/enterprise-cloud@latest/rest/orgs/orgs?apiVersion=2022-11-28#get-the-audit-log-for-an-organization
• https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#using-the-audit-log-api

This PR adds this new rate limit category.

I have a use case where I need to know the rate limit category before making the request so as to not reimplement what's already done in go-github, I made this logic public. Other users could also benefit of this change.
If you think it's not reasonable and it should be kept private, I will revert this change.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.87%. Comparing base (2b8c7fa) to head (c483b01).
Report is 23 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #3088 +/- ##
==========================================
- Coverage 97.72% 92.87% -4.86% 
==========================================
Files 153 170 +17 Lines 13390 11404 -1986 ==========================================
- Hits 13085 10591 -2494 - Misses 215 723 +508 
Partials 90 90 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Letiste]

@gmlewis could you take a look at this when you have some time? 🙏 (I'm notifying you as you seem to review the recent PRs, sorry if you are not the correct person for that).
Let me know if I need to clarify some things.
Not sure as well why the codecov is failing here, I thought I added all the necessary tests related to my changes but maybe I missed some

[gmlewis]

@gmlewis could you take a look at this when you have some time? 🙏 (I'm notifying you as you seem to review the recent PRs, sorry if you are not the correct person for that). Let me know if I need to clarify some things. Not sure as well why the codecov is failing here, I thought I added all the necessary tests related to my changes but maybe I missed some

Hi @Letiste - I apologize for not seeing this two weeks ago. I'm not sure how I missed it. 😞

Don't worry about the codecov - it has lately been really flakey.

I'll take a look at the PR.

[gmlewis]

Thank you, @Letiste !
LGTM.

Awaiting second LGTM+Approval from any other contributor to this repo before merging.

[gmlewis]

Thank you, @rpelliard !
Merging.