FR: support for cross-fork stacked PRs

The limitation that the source and target branch need to be on the same repository is a showstopper for my project's use of stacked PRs, and I expect it will similarly be so for almost any github project of nontrivial size. It's unreasonable to expect projects to grant all potential contributors branch creation permission, and my project would similarly consider it unreasonable to restrict stacked PR support to just some subset of trusted developers -- we don't want some developers to feel "second-class" to the extent we can avoid it.

I can understand how this restriction would arise -- presumably the repository associated with a PR is always the repository of the base branch, which requires the base branch (the previous PR in the stack) to be in the target repository for a stacked PR. But please consider ways in which it could be lifted, as the current limitation is a severe blocker to usage of this functionality.

En el issue no se mencionan archivos fuente ni pruebas. Empieza rastreando cómo gh-stack asocia un pull request con su repositorio base y valida ramas apiladas entre forks. Se considera terminado cuando un contribuyente puede crear y usar un PR apilado cuyas ramas de origen y destino están en repositorios diferentes, sin necesitar permisos para crear ramas en el repositorio de destino.

Escrito por el modelo de indexación a partir del texto del issue.