Is your feature request related to a problem? Please describe.
When a push fails due to rate limit, it looks like the error does not show up in the app logs. This may be a little tough to test on our end with real GitHub, may need to use testing mocks.
@nikellepetrillo may have a screenshot that indicates whether a) an error is logged that does not mention rate limit or b) no message is logged at all

Describe the solution you'd like
A message indicating the rate limit error linking to docs.dockstore.org and some troubleshooting options/workarounds from https://oicr.slack.com/archives/C01T4BV0GAE/p1754056800578829

Describe alternatives you've considered
Further tinker with and optimize some of the strategies we use to reduce the use of rate limit. There are some caching options using conditional requests https://docs.github.com/en/rest/using-the-rest-api/best-practices-for-using-the-rest-api?apiVersion=2022-11-28#use-conditional-requests-if-appropriate that may not be optimized across multiple webservice containers. That said, there will always be a limit of some kind so we should have a more graceful experience in that case.

Additional context

[Domain] - https://dockstore.org

Webservice - 1.17.2

UI - 2.14.1

Deploy - 1.17.0

┆Issue is synchronized with this Jira Story
┆Issue Number: DOCK-2620
┆Sprint: Backlog
┆Issue Type: Story