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.

检查 .github/workflows/ci.yml 的第 72-73 行，并查阅 issue 中链接的有关 GitHub Actions fork 和 secrets 的文档。验证来自本地 fork 的 pull request 的 workflow 行为；完成的标准是，ember-cli-update CI job 不再仅仅因为 fork 无法访问所引用的 secret 而失败。

由索引模型根据 Issue 内容生成。