[Feature]: To be able to specify a user login for github api calls

### User story

With more than about 3 servers on 1 IP, the anonymous api calls is ratelimited to 60 per hour

### Game

Rust

### Linux distro

Other

### Command

command: mods-update

### Further information

I run 9 servers in total and the ratelimit is killing me during server wipes and updates. Each time mods-update is run, it performs about 11 api calls. This would allow at most 5 servers on the same IP before ratelimiting starts to interfere. If I could specify a user for the api calls to use (I'd be happy to specify my own) then the ratelimit goes up to 5,000 which is more than enough.

The error you see when you have exhausted your limit is

jq: error (at :1): Cannot iterate over null (null)
jq: error (at :1): Cannot iterate over null (null)

which doesn't really indicate what the real reason for the failure is.

I briefly looked through the scripts and it doesn't look like this feature currently exists.

Github rate limits are described here

https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28

Inizia con il comando mods-update e traccia le chiamate all’API GitHub che portano all’errore null di jq segnalato. Esamina la documentazione di GitHub collegata sui limiti di frequenza e definisci come dovrebbe essere fornito un login utente configurabile e come dovrebbero essere segnalati i limiti esauriti; il lavoro è completato quando le chiamate autenticate funzionano per questo comando e gli errori identificano la causa relativa al limite di frequenza.

Scritto dal modello di indicizzazione a partire dal testo della issue.