Handle the error for contribution Graph

As you know, the graph needs an `API key` with all the necessary permissions but after an hour or an half it looks like its `API key` get expires and generating a new key will make it work, but with the old one can still get `header information`
find a solution for it, or make it expires later.

Start by reproducing the contribution graph request with an old API key and a newly generated key, then inspect the GitHub API authentication handling in the CLI. Done means the graph either continues working for the intended key lifetime or reports the expiration clearly and provides a reliable recovery path.

Written by the indexing model from the issue text.