tracking-issue: Fix outstanding graphql errors

Created by: efritz

Note: The proper read for "fix" here should be incredulous.

Running locally and sometimes in actions I still see some graphql errors with a GitHub possible timeout message. I think this can only come from the load issues query (as list and update issues are relatively small payloads). I'm breaking this query down a bit to see if this lowers the error rate, and tagging the other errors so we know if it's a problem with this one or not.