CI Failures from forks

Folks sending in a PR from their local forks will always cause a failure of the `ember-cli-update` CI job. This is due to the usage of `${{ secrets.GitHubToken }}` here:

https://github.com/ember-cli/ember-cli-update/blob/fc221be115e87049427d33f17cf11879637ea9c7/.github/workflows/ci.yml#L72-L73

Pull requests from forks will not have access to any `${{ secrets.* }}` content (for somewhat clear security reasons).

See [documentation here](https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets#using-encrypted-secrets-in-a-workflow), which starts out with:

> With the exception of GITHUB_TOKEN, secrets are not passed to the runner when a workflow is triggered from a forked repository.

Ispeziona .github/workflows/ci.yml alle righe 72-73 e consulta la documentazione di GitHub Actions su fork e secrets collegata nell’issue. Verifica il comportamento del workflow per le pull request provenienti da fork locali; è completato quando il job CI di ember-cli-update non fallisce più esclusivamente perché il fork non può accedere al secret referenziato.

Scritto dal modello di indicizzazione a partire dal testo della issue.