Repository Credentials Unreliably Support Github App

[Drulikar]

Describe the bug
(This is the same bug has already been described in DMs)
When using a Github APP for authentication (even one that has full permissions (including repo access), log will frequently mention Requested GitHub client has no requests remaining! This seems to be preventing the DMAPI update PR from being created, github.qkg1.topments to be created for a TM, and possibly make github deployment updates unreliable (but this did seem to work atleast sometimes). Using a PAT token is fine however.

To Reproduce
Steps to reproduce the behavior:

1. Go to an instance's repository tab.
2. Reset credentials & Save
3. Set up credentials to use a Github app & Save
4. Use these settings

5. Compile & Deploy some TMs
6. Check if you got a deployment posted on github (likely), Check if your TMs got comments (unlikely)

Expected behavior
Github App credentials to have the same capability as a PAT (though keep in mind we do use this same app for CI - but I'm skeptical its being used so much its rate limited every time TGS is trying to use it).

Logs
See DMs or
tgs-20260210.log
(of note when you see Failed to parse PEM! in logs thats when I tried a key without the PRIVATE KEY START/END headers)

Server State: (please complete the following information):

• OS: Debian 13.3
• Version: TGS Version 6.19.1 and 6.19.2
• Database Type/Version: MySQL 8
• BYOND Version Used: 516.1667
• git Repository Used: CMSS13
• Origin Commit hash Used: 3d1ec05 and many others
• Active Test Merges: Should be irrelevant but:

• Client Version: v6.11.3 (GITHUB)

Additional context
See DMs.
App settings tried:

and

[Drulikar]

Sorry the DMAPI thing is likely unrelated - I forgot it was an action and not something TGS would trigger; but then weird why it too has become unreliable for us too. cmss13-devs/cmss13@1fdb6a3 so far has been unsuccessful w/ getting the action to trigger on its own. See https://github.com/cmss13-devs/cmss13/actions/workflows/update_tgs_dmapi.yml Need be I can just trigger it manually - just weird.