Get number of issue per dependency in our `dependency-discovery` service

[Kevan-Y]

After the dependencies page was added in this https://github.com/Seneca-CDOT/telescope/issues/3357. We can improve our dependency-discovery service to get the number of issues each of these dependencies has, and use that to sort the list in the front-end. see comment

We might be able to use our parser services to retrieve the GitHub issues and store them in Redis for catching. This way we don't get a rate limit with GitHub API so often.