Fix and Improvements Github LOC

[gabrielsoltz]

The github_com.sh has several bugs and problems:

• The code was not iterating across pages when repositories were paginated (more than 100); it was only reading from the page hardcoded in the code, so, for example, following the readme example, if you use (# Example for 150 repos: GetAPI="orgs/$org/repos?per_page=100&page=2") you will only get the last 50 repositories, missing 100.
• The code was counting archived repositories, which makes no sense for integrating with Sonarqube
• The code needed to be hardcoded when you have more repositories than 100

Now, when no repository is passed as an argument, the code will count the total amount of repositories in GitHub and, based on that, configure itself for iterating/paginating the results. You don't need to hardcode the code anymore. If a repository is passed as an argument, it will only scan that repository (as before).

The code is now also parsing each repository's archived field. If the repository is archived, it will not be analyzed.

[sylvain-combe-sonarsource]

Hi @gabrielsoltz It may take some time for us to validate your PR, but many thanks for assembling it.

@emmanuel-colussi-sonarsource I believe we had the possibility to recurse in GitHub paginated answers, and it looks like we had a regression with one of your commits. The easiest fix is probably to merge this PR, and benefit from this new filter on archived projects in the process :-)