Optimize GitHub app RepositoryNode

Community & Support: [LinkedIn Group](https://www.linkedin.com/groups/14656108/) · [Slack #project-nest](https://owasp.slack.com/archives/project-nest)

Active project leaders: Arkadii Yakovets -- [GitHub](https://github.com/arkid15r/) · [LinkedIn](https://www.linkedin.com/in/arkid15r/) · [Slack](https://owasp.slack.com/team/U060W3NKLTF); Kate Golovanova -- [GitHub](https://github.com/kasya/) · [LinkedIn](https://www.linkedin.com/in/kate-golovanova/) · [Slack](https://owasp.slack.com/team/U07PWB1JZ6Z)

[Contributing](https://github.com/owasp/nest/blob/main/CONTRIBUTING.md) · [Code of Conduct](https://github.com/owasp/nest/blob/main/CODE_OF_CONDUCT.md) · [GSoC Mentors](https://github.com/owasp/nest/blob/main/MENTORS.md)

---

**Describe the solution you'd like**

1.​ New loader for issues to load based on repositories IDs (repositories_issues_loader)
2.​ New loader for releases (repositories_releases_loader) for the latest_release resolver.
3.​ Loader for the project resolver, and it will be used for the ReleaseNode.
4.​ New loader for recent_milestones.
5.​ Loader for releases resolver (The exact loader for latest release)

and for the top_contributors, I will leave it for a separate issue in the end of the dataloaders stage as it is common through the GraphQL nodes and I will need to discuss with mentors about the appropriate way to refactor the top_contributors function.

**Are you going to work on implementing this?**

- [x] Yes
- [ ] No

**Additional context**
Add any other context or screenshots about the feature request here.